Skip to content
cccskills
FreePublished on GitHub

trade-outreach-email

Generate conservative, editable English outreach drafts for foreign-trade sales from structured lead inputs and customer-intel signals. Use when an operator needs a first-touch or follow-up email draft that calls confirmed recent/customer-market signals from the customer-intel Skill, with subject options, review notes, and explicit reminders not to present unconfirmed facts as facts.

The English summary is being prepared. Showing the original description.

Run score Not tested

See how to install

Files included (38)

  • SKILL.md5.6 KB
  • .gitignore29 B
  • examples/customer-intel-bridged-email-input.json11.1 KB
  • examples/customer-intel-report.json17.2 KB
  • examples/first-touch-output.json2.5 KB
  • examples/first-touch-output.md2.3 KB
  • examples/first-touch.json621 B
  • examples/follow-up-output.json2.9 KB
  • examples/follow-up-output.md2.7 KB
  • examples/follow-up.json737 B
  • examples/solar-first-touch-output.json2.8 KB
  • examples/solar-first-touch-output.md2.6 KB
  • examples/solar-first-touch.json709 B
  • examples/textile-follow-up-output.json3.1 KB
  • examples/textile-follow-up-output.md2.8 KB
  • examples/textile-follow-up.json819 B
  • for-openclaw/examples/sample-input.json3.1 KB
  • for-openclaw/examples/sample-output.json7.1 KB
  • for-openclaw/examples/sample-output.md3.1 KB
  • for-openclaw/README.md2.3 KB
  • for-openclaw/references/runtime-rules.md728 B
  • for-openclaw/schemas/openclaw-email-input.json1.9 KB
  • for-openclaw/scripts/build_email_draft_from_openclaw.py15.3 KB
  • for-openclaw/SKILL.md3.2 KB
  • LICENSE1.0 KB
  • README.md3.6 KB
  • references/customer-intel-integration.md1.9 KB
  • references/input-fields.md2.2 KB
  • references/output-template.md927 B
  • references/review-rules.md546 B
  • schemas/email-draft-input.schema.json2.5 KB
  • scripts/build_email_draft.py29.9 KB
  • scripts/build_email_input_from_customer_intel.py20.5 KB
  • scripts/build_feishu_stage_payload.py1.9 KB
  • scripts/run_pre_release_gate.py2.3 KB
  • scripts/run_regression_checks.py26.0 KB
  • 立项方案.md465 B
  • 验收记录.md338 B

SKILL.md (original)

Review the instructions the agent will receive before you install.

开发信 Skill

Overview

用这个 Skill 把结构化客户信息和客户背调信号转换成可人工修改后发送的英文邮件草稿。

当前定位:复核型开发信工作台

角色定位:

  • 开发信策略员
  • 上游:人工整理输入,或 客户背调skill/ 输出的桥接结果
  • 下游:人工复核与实际发送动作
  • 不负责自动发送,也不负责替代上游做搜索、初筛和背调
  • 不负责重新查“客户最近发生了什么”;近期动态、市场变化和销售切入点必须来自 客户背调skill/

当前只覆盖两个场景:

  • first_touch:首轮开发信
  • follow_up:跟进邮件

它不是自动发送工具。目标是把零散输入整理成更稳定、更易复核的英文草稿。

Standard Input

输入统一为 JSON:

{
  "email_type": "first_touch",
  "customer_name": "Anna",
  "company_name": "Acme Foods",
  "product_or_offer": "frozen mixed vegetables",
  "goal": "introduce our factory and ask whether they are open to new suppliers",
  "country_or_market": "Poland",
  "customer_profile_summary": "Company website shows private-label frozen food focus in EU retail.",
  "previous_contact_context": "",
  "tone": "professional,warm",
  "sender_name": "Leo",
  "sender_company": "Ningbo FreshGrow Foods",
  "signature": "",
  "constraints": ""
}

Workflow

  1. Normalize the input fields.
  2. Validate the input against the local JSON schema and confirm email_type is first_touch or follow_up.
  3. When source_context comes from customer intel, require draft_authorization = approved and one approved selected_sales_angle.
  4. Build subject options based on scenario, product, and company name.
  5. Generate one main draft and one lighter alternative draft.
  6. Preserve the selected ANGLE-*, CL-*, and EV-* references in the review package.
  7. Attach review notes for any claim that depends on summary, historical context, pricing, capability, or other unconfirmed details.
  8. If source_context includes recent customer signals or market signals, use them only when a dated source URL and medium/high confidence are present.
  9. Output in the structure defined in output-template.md.

Output Requirements

  • 必须包含邮件类型
  • 必须包含 2 个标题候选
  • 必须包含至少 1 个英文正文草稿
  • 必须包含中文复核提示
  • 必须包含 evidence_signals_used
  • 必须包含 unconfirmed_fact_checklist
  • 必须包含 send_policy = manual_review_only
  • 公司级线索缺少联系人时使用自然的公司团队称呼;不得输出 Dear there、Dear unknown 等占位语
  • 最终 JSON 必须保留批准的 ANGLE-*、对应 CL-* 与 EV-* 结构化对象,不只保留文本摘要
  • 批准角度属于内部策略与审计上下文,不得把 Open by...、Connect the note... 等写作指令原样复制到客户正文
  • 工业场景默认只使用通用应用与参数确认表达;BOM、automation module、motor/drive、ASRS 或物料搬运等细节必须同时有上游主张和证据支持
  • follow_up 必须消费真实 previous_contact_context;缺失时阻断,不得自动补写历史沟通
  • follow_up 默认只承诺产品详情与规格;只有卖方能力、证明或授权资料明确支持样品时才能使用 sample 表达
  • 必须包含 workflow_guidance
  • 必须回显关键输入依据
  • 如引用近期动态、市场变化或合规信号,必须来自上游 source_context
  • 背调桥接场景必须有明确批准的销售角度;未批准时脚本直接拦截,不生成草稿
  • 必须保留被选中的 claim 和 evidence,而不是只传来源标题
  • 不能把不确定信息写成确定事实
  • 不能越权替代人工执行发送
  • 不能越权替代 客户背调skill/ 编造客户事实
  • 不能自行生成“客户最近发生了什么”
  • 不能把弱证据包装成个性化事实

Main Script

默认脚本入口是 build_email_draft.py。

Example

python3 ./scripts/build_email_draft.py --input-json ./examples/first-touch.json
python3 ./scripts/run_regression_checks.py

Defaults

  • 本地模板生成优先
  • 不强依赖联网
  • 不联网背调;只消费输入和 source_context
  • 输出默认偏保守
  • 不覆盖报价邮件
  • 发送前必须人工复核
  • 默认下游动作:ready_for_manual_send | hold_for_manual_review

Table and Rule Capture

  • 本 Skill 输出开发信草稿和复核清单能力,不要求企业使用固定邮件结果表。
  • 写入企业表格、知识库或邮箱草稿箱时,先沿用已有表头和归口,再映射标题候选、草稿引用、近期信号、市场信号、证据依据、待确认项、发送策略等标准字段。
  • 用户没有可用表格时,龙虾可以按企业产品、市场和跟进流程新建够用表。
  • 当用户确认新的开发信风格、禁用表达、行业话术、跟进节奏或表头映射后,必须追问:是否更新到对应 Skill 以便下次自动复用。真实写入必须得到用户授权。

Enhancement Entry

如需数据留存、统一编排、多代理协作或飞书落地,请查看飞书文档:

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Run or resume a deliverable active-outreach workflow across lead discovery, screening, customer intel, and outreach email. Use when an operator or system pipeline needs durable run state, visible intermediate artifacts, evidence gates, report-bound human approval, and a final editable email draft that is never auto-sent.

The English summary is being prepared. Showing the original description.

FloydTang/trade-skills-collection14Updated Aug 26, 2026

Build bilingual, evidence-backed, SIEGER v2 customer intelligence reports for foreign-trade leads. Use when OpenClaw or a sales operator needs claim-level citations, decision gates, an industry-specific analysis lens, a non-fabricated verdict card, and sales angles that require approval before downstream outreach drafting.

The English summary is being prepared. Showing the original description.

FloydTang/trade-skills-collection14Updated Aug 26, 2026

OpenClaw-native SIEGER-aligned customer intelligence. Use a structured evidence bundle to produce a bilingual report with claim-level evidence, decision gates, industry-specific analysis, and proposed sales angles that require explicit approval before email drafting.

The English summary is being prepared. Showing the original description.

FloydTang/trade-skills-collection14Updated Aug 26, 2026

Find the first batch of foreign-trade prospect companies from public web, LinkedIn, and user-authorized data sources such as customs exports, trade show lists, association directories, CRM/Excel files, or historical customer data, then output a conservative, structured candidate list ready for lead screening.

The English summary is being prepared. Showing the original description.

FloydTang/trade-skills-collection14Updated Aug 26, 2026

Discover prospect companies from a structured OpenClaw search brief, including public search and user-authorized data sources, then output a conservative candidate list ready for lead screening.

The English summary is being prepared. Showing the original description.

FloydTang/trade-skills-collection14Updated Aug 26, 2026

Normalize and screen scattered foreign-trade leads into a conservative, structured lead pool that can flow into customer-intel research. Use when an operator has company names, websites, emails, or contact clues from search results and needs a standardized output with missing-field warnings, review flags, next-step suggestions, and customer-intel-ready JSON.

The English summary is being prepared. Showing the original description.

FloydTang/trade-skills-collection14Updated Aug 26, 2026

See all skills by FloydTang

Report a problem with this skill