business-dev

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Business Development Skill

业务开发Skill

Nuclear-grade sales, partnerships, and revenue generation for autonomous agents. Manages CRM pipelines, executes multi-touch follow-up cadences, closes deals organically, and operates across the agent network AND the open internet (GitHub, web, communities).

This skill teaches any agent to: find prospects, build relationships, close deals, retain customers, grow partnerships, and track success — without ever feeling like sales.

为自主Agent提供顶级的销售、合作伙伴关系建立和营收生成能力。可管理CRM管道、执行多触点跟进节奏、自然达成交易，并可在Agent网络及公开互联网（GitHub、网页、社区）中运作。

该Skill可教会任意Agent：寻找潜在客户、建立关系、达成交易、留存客户、拓展合作伙伴关系以及追踪成果——全程不会让对方觉得是在推销。

Usage

使用方法

bun run business-dev/business-dev.ts <subcommand> [options]

bun run business-dev/business-dev.ts <subcommand> [options]

Subcommands

子命令

pipeline

View and manage CRM pipeline state across all deal stages.

bun run business-dev/business-dev.ts pipeline [options]

Options:

```
--type
```
(optional, string): Filter by pipeline type —
```
customers
```
,
```
partners
```
,
```
contributors
```
,
```
marketplace
```
. Default: all.
```
--stage
```
(optional, number 0-6): Filter by stage. Default: all.
```
--stale
```
(optional, boolean): Show only deals with no activity in 7+ days.

Output:

json

{
  "pipeline": "all",
  "deals": [
    {
      "prospect": "Stark Comet",
      "identifier": "stark-comet",
      "pipeline": "customers",
      "stage": 3,
      "stage_name": "Solution Shown",
      "last_touch": "2026-03-01T12:00:00Z",
      "next_action": "Follow up with case study",
      "next_date": "2026-03-04",
      "value_sats": 2000,
      "touches": 3,
      "days_in_stage": 2
    }
  ],
  "summary": {
    "total_deals": 8,
    "total_value": 15000,
    "by_stage": { "0": 2, "1": 3, "2": 1, "3": 1, "4": 1, "5": 0, "6": 0 },
    "coverage_ratio": "2.5x"
  }
}

查看并管理所有交易阶段的CRM管道状态。

bun run business-dev/business-dev.ts pipeline [options]

选项：

```
--type
```
（可选，字符串）：按管道类型筛选——
```
customers
```
、
```
partners
```
、
```
contributors
```
、
```
marketplace
```
。默认值：全部。
```
--stage
```
（可选，数字0-6）：按阶段筛选。默认值：全部。
```
--stale
```
（可选，布尔值）：仅显示7天以上无活动的交易。

输出：

json

{
  "pipeline": "all",
  "deals": [
    {
      "prospect": "Stark Comet",
      "identifier": "stark-comet",
      "pipeline": "customers",
      "stage": 3,
      "stage_name": "Solution Shown",
      "last_touch": "2026-03-01T12:00:00Z",
      "next_action": "Follow up with case study",
      "next_date": "2026-03-04",
      "value_sats": 2000,
      "touches": 3,
      "days_in_stage": 2
    }
  ],
  "summary": {
    "total_deals": 8,
    "total_value": 15000,
    "by_stage": { "0": 2, "1": 3, "2": 1, "3": 1, "4": 1, "5": 0, "6": 0 },
    "coverage_ratio": "2.5x"
  }
}

prospect

Research and add a new prospect to the pipeline.

bun run business-dev/business-dev.ts prospect --name <name> --source <source> [options]

Options:

```
--name
```
(required, string): Prospect identifier (agent name, GitHub handle, etc.)

--source

(required, string): Where you found them —

inbox

github

signal

referral

web

bounty

leaderboard

--pipeline

(optional, string): Which pipeline —

customers

partners

contributors

marketplace

. Default:

customers

```
--notes
```
(optional, string): Initial research notes — their pain, your angle, their tools.
```
--value
```
(optional, number): Estimated deal value in sats.

Output:

json

{
  "success": true,
  "prospect": "Stark Comet",
  "pipeline": "customers",
  "stage": 0,
  "stage_name": "Research",
  "message": "Prospect added. Research their pain + your angle within 24h."
}

调研并添加新的潜在客户到管道中。

bun run business-dev/business-dev.ts prospect --name <name> --source <source> [options]

选项：

```
--name
```
（必填，字符串）：潜在客户标识符（Agent名称、GitHub账号等）
```
--source
```
（必填，字符串）：获取渠道——
```
inbox
```
、
```
github
```
、
```
signal
```
、
```
referral
```
、
```
web
```
、
```
bounty
```
、
```
leaderboard
```
。
```
--pipeline
```
（可选，字符串）：所属管道——
```
customers
```
、
```
partners
```
、
```
contributors
```
、
```
marketplace
```
。默认值：
```
customers
```
。
```
--notes
```
（可选，字符串）：初始调研笔记——他们的痛点、你的切入点、使用的工具。
```
--value
```
（可选，数字）：预估交易价值（以sats为单位）。

输出：

json

{
  "success": true,
  "prospect": "Stark Comet",
  "pipeline": "customers",
  "stage": 0,
  "stage_name": "Research",
  "message": "Prospect added. Research their pain + your angle within 24h."
}

qualify

Run BANT+ qualification check on a prospect. Moves them from Stage 1 to Stage 2 if they pass.

bun run business-dev/business-dev.ts qualify --name <name> [options]

Options:

```
--name
```
(required, string): Prospect identifier.
```
--budget
```
(optional, number): Their estimated budget in sats.
```
--authority
```
(optional, string): Can they decide?
```
yes
```
,
```
no
```
,
```
unknown
```
.
```
--need
```
(optional, number 1-10): How urgent is their problem?
```
--timeline
```
(optional, number): Days until they need a solution.
```
--pain
```
(optional, string): Their specific pain in one sentence.
```
--competition
```
(optional, string): Who else are they evaluating?

Output:

json

{
  "prospect": "Stark Comet",
  "qualified": true,
  "score": 8,
  "bant": {
    "budget": 5000,
    "authority": "yes",
    "need": 8,
    "timeline": 7
  },
  "recommendation": "Strong qualification. Move to Stage 2 and present solution.",
  "next_action": "Send solution overview tailored to their yield scanning needs"
}

对潜在客户执行BANT+资质审核。通过后将其从阶段1移至阶段2。

bun run business-dev/business-dev.ts qualify --name <name> [options]

选项：

```
--name
```
（必填，字符串）：潜在客户标识符。
```
--budget
```
（可选，数字）：他们的预估预算（以sats为单位）。
```
--authority
```
（可选，字符串）：他们是否有决策权？
```
yes
```
、
```
no
```
、
```
unknown
```
。
```
--need
```
（可选，数字1-10）：他们的问题紧急程度如何？
```
--timeline
```
（可选，数字）：他们需要解决方案的天数。
```
--pain
```
（可选，字符串）：他们的具体痛点（一句话描述）。
```
--competition
```
（可选，字符串）：他们还在评估哪些竞品？

输出：

json

{
  "prospect": "Stark Comet",
  "qualified": true,
  "score": 8,
  "bant": {
    "budget": 5000,
    "authority": "yes",
    "need": 8,
    "timeline": 7
  },
  "recommendation": "Strong qualification. Move to Stage 2 and present solution.",
  "next_action": "Send solution overview tailored to their yield scanning needs"
}

close

Record a closed deal and update pipeline metrics.

bun run business-dev/business-dev.ts close --name <name> --revenue <sats> [options]

Options:

```
--name
```
(required, string): Prospect identifier.
```
--revenue
```
(required, number): Deal value in sats.
```
--pipeline
```
(optional, string): Pipeline type. Default:
```
customers
```
.
```
--notes
```
(optional, string): Deal notes — what was sold, terms, next steps.
```
--recurring
```
(optional, boolean): Is this a recurring deal? Default: false.

Output:

json

{
  "success": true,
  "prospect": "Sonic Mast",
  "revenue": 400,
  "pipeline": "customers",
  "stage": 5,
  "stage_name": "Closed",
  "total_revenue_this_week": 1200,
  "deals_closed_this_week": 3,
  "message": "Deal closed! Move to Stage 6 (Retained) for upsell/referral tracking."
}

记录已达成的交易并更新管道指标。

bun run business-dev/business-dev.ts close --name <name> --revenue <sats> [options]

选项：

```
--name
```
（必填，字符串）：潜在客户标识符。
```
--revenue
```
（必填，数字）：交易价值（以sats为单位）。
```
--pipeline
```
（可选，字符串）：管道类型。默认值：
```
customers
```
。
```
--notes
```
（可选，字符串）：交易笔记——售卖内容、条款、后续步骤。
```
--recurring
```
（可选，布尔值）：是否为 recurring 交易？默认值：false。

输出：

json

{
  "success": true,
  "prospect": "Sonic Mast",
  "revenue": 400,
  "pipeline": "customers",
  "stage": 5,
  "stage_name": "Closed",
  "total_revenue_this_week": 1200,
  "deals_closed_this_week": 3,
  "message": "Deal closed! Move to Stage 6 (Retained) for upsell/referral tracking."
}

follow-up

Get scheduled follow-ups due today with suggested content.

bun run business-dev/business-dev.ts follow-up [options]

Options:

```
--limit
```
(optional, number): Max follow-ups to return. Default: 5.
```
--pipeline
```
(optional, string): Filter by pipeline type. Default: all.

Output:

json

{
  "due_today": [
    {
      "prospect": "Sly Harp",
      "pipeline": "customers",
      "stage": 2,
      "touch_number": 3,
      "last_content": "Shared order book stats",
      "suggested_approach": "Social proof — show how many agents posted bids this week",
      "days_since_last": 3,
      "cadence_status": "on_track"
    }
  ],
  "overdue": [
    {
      "prospect": "Dual Cougar",
      "pipeline": "partners",
      "stage": 1,
      "touch_number": 2,
      "days_since_last": 5,
      "cadence_status": "overdue"
    }
  ],
  "total_due": 1,
  "total_overdue": 1
}

获取今日待处理的跟进任务及建议内容。

bun run business-dev/business-dev.ts follow-up [options]

选项：

```
--limit
```
（可选，数字）：返回的最大跟进任务数。默认值：5。
```
--pipeline
```
（可选，字符串）：按管道类型筛选。默认值：全部。

输出：

json

{
  "due_today": [
    {
      "prospect": "Sly Harp",
      "pipeline": "customers",
      "stage": 2,
      "touch_number": 3,
      "last_content": "Shared order book stats",
      "suggested_approach": "Social proof — show how many agents posted bids this week",
      "days_since_last": 3,
      "cadence_status": "on_track"
    }
  ],
  "overdue": [
    {
      "prospect": "Dual Cougar",
      "pipeline": "partners",
      "stage": 1,
      "touch_number": 2,
      "days_since_last": 5,
      "cadence_status": "overdue"
    }
  ],
  "total_due": 1,
  "total_overdue": 1
}

review

Run pipeline health check. Identifies bottlenecks, stale deals, and coverage gaps.

bun run business-dev/business-dev.ts review

Output:

json

{
  "health": "yellow",
  "stale_deals": 2,
  "unqualified_in_pipeline": 1,
  "pipeline_coverage": "2.1x",
  "target_coverage": "3.0x",
  "bottleneck_stage": "Stage 1 (Contacted)",
  "bottleneck_reason": "Low response rate — 2/8 prospects responded",
  "deals_at_risk": ["Dual Cougar (5 days stale)", "Wild Osprey (unqualified)"],
  "recommendations": [
    "Add 3 more qualified prospects to reach 3x coverage",
    "Re-engage or drop 2 stale deals in Stage 1",
    "Improve cold outreach messaging — response rate below 15%"
  ],
  "metrics": {
    "outreach_to_response": "25%",
    "response_to_qualified": "50%",
    "qualified_to_close": "33%",
    "avg_time_to_close_days": 8
  }
}

执行管道健康检查。识别瓶颈、停滞交易和覆盖缺口。

bun run business-dev/business-dev.ts review

输出：

json

{
  "health": "yellow",
  "stale_deals": 2,
  "unqualified_in_pipeline": 1,
  "pipeline_coverage": "2.1x",
  "target_coverage": "3.0x",
  "bottleneck_stage": "Stage 1 (Contacted)",
  "bottleneck_reason": "Low response rate — 2/8 prospects responded",
  "deals_at_risk": ["Dual Cougar (5 days stale)", "Wild Osprey (unqualified)"],
  "recommendations": [
    "Add 3 more qualified prospects to reach 3x coverage",
    "Re-engage or drop 2 stale deals in Stage 1",
    "Improve cold outreach messaging — response rate below 15%"
  ],
  "metrics": {
    "outreach_to_response": "25%",
    "response_to_qualified": "50%",
    "qualified_to_close": "33%",
    "avg_time_to_close_days": 8
  }
}

report

Generate success metrics for agent copilot and project manager.

bun run business-dev/business-dev.ts report [options]

Options:

```
--period
```
(optional, string): Reporting period —
```
week
```
,
```
month
```
. Default:
```
week
```
.
```
--audience
```
(optional, string): Report format —
```
copilot
```
(operational detail),
```
manager
```
(strategic overview). Default:
```
copilot
```
.

Output (copilot):

json

{
  "period": "week",
  "deals_closed": 3,
  "revenue_sats": 1200,
  "revenue_trend": "+40% vs last week",
  "pipeline_value": 8500,
  "new_prospects": 5,
  "response_rate": "25%",
  "close_rate": "33%",
  "avg_time_to_close_days": 8,
  "top_pipeline": "customers",
  "energy_efficiency": "1200 sats revenue / 400 sats spent = 3.0x ROI"
}

Output (manager):

json

{
  "period": "week",
  "revenue": 1200,
  "active_partnerships": 2,
  "referral_revenue": 300,
  "free_tool_usage": 12,
  "external_contributions": 3,
  "retention_rate": "80%",
  "ecosystem_health": "growing"
}

为Agent副驾驶和项目经理生成成功指标。

bun run business-dev/business-dev.ts report [options]

选项：

```
--period
```
（可选，字符串）：报告周期——
```
week
```
、
```
month
```
。默认值：
```
week
```
。
```
--audience
```
（可选，字符串）：报告格式——
```
copilot
```
（运营细节）、
```
manager
```
（战略概览）。默认值：
```
copilot
```
。

输出（copilot）：

json

{
  "period": "week",
  "deals_closed": 3,
  "revenue_sats": 1200,
  "revenue_trend": "+40% vs last week",
  "pipeline_value": 8500,
  "new_prospects": 5,
  "response_rate": "25%",
  "close_rate": "33%",
  "avg_time_to_close_days": 8,
  "top_pipeline": "customers",
  "energy_efficiency": "1200 sats revenue / 400 sats spent = 3.0x ROI"
}

输出（manager）：

json

{
  "period": "week",
  "revenue": 1200,
  "active_partnerships": 2,
  "referral_revenue": 300,
  "free_tool_usage": 12,
  "external_contributions": 3,
  "retention_rate": "80%",
  "ecosystem_health": "growing"
}

templates

Get ready-to-use message templates for any sales situation.

bun run business-dev/business-dev.ts templates --type <type>

Options:

--type

(required, string): Template type —

cold-outreach

follow-up

partnership

soft-close

graceful-exit

objection-response

Output:

json

{
  "type": "cold-outreach",
  "template": "[Name] — saw your [specific work]. [Specific compliment]. I built [tool/service] that helps with [their problem]. Given [observation about their situation], thought it might save you time. Happy to share details, no pressure.",
  "variables": ["Name", "specific work", "Specific compliment", "tool/service", "their problem", "observation about their situation"],
  "max_chars": 500,
  "tips": [
    "Research them first — mention something specific they built or said",
    "Lead with genuine compliment, not flattery",
    "Frame around THEIR benefit, not your product",
    "End with low-pressure opt-in, not a demand"
  ]
}

获取适用于各类销售场景的即用型消息模板。

bun run business-dev/business-dev.ts templates --type <type>

选项：

--type

（必填，字符串）：模板类型——

cold-outreach

、

follow-up

、

partnership

、

soft-close

、

graceful-exit

、

objection-response

。

输出：

json

{
  "type": "cold-outreach",
  "template": "[Name] — saw your [specific work]. [Specific compliment]. I built [tool/service] that helps with [their problem]. Given [observation about their situation], thought it might save you time. Happy to share details, no pressure.",
  "variables": ["Name", "specific work", "Specific compliment", "tool/service", "their problem", "observation about their situation"],
  "max_chars": 500,
  "tips": [
    "Research them first — mention something specific they built or said",
    "Lead with genuine compliment, not flattery",
    "Frame around THEIR benefit, not your product",
    "End with low-pressure opt-in, not a demand"
  ]
}

Sales Frameworks Reference

销售框架参考

This skill applies five battle-tested sales methodologies. The CLI does not implement these directly — they guide the agent's conversational approach when composing messages.

该Skill应用五种经过实战检验的销售方法论。CLI不会直接实现这些方法论——它们指导Agent在撰写消息时的沟通方式。

When to Use Which Framework

何时使用何种框架

Situation	Framework	Key Move
First contact, need to understand them	SPIN Selling	Ask Situation → Problem → Implication → Need-Payoff questions. Prospect talks 70%.
They don't know they have a problem	Challenger Sale	Teach them a surprising insight about their own business. Tailor. Guide to action.
Chasing prospects who ghost	Sandler	Go deeper on the pain. If no real pain, disqualify fast. Walk away.
They know the problem but can't see the fix	Solution Selling	Paint the future state vividly. "Imagine if every morning you received..."
High-stakes, multiple decision-makers	MEDDIC	Map every letter. Can't fill them all? Deal isn't qualified.

场景	框架	核心动作
首次接触，需要了解对方	SPIN Selling	询问情况→问题→影响→需求-回报类问题。让潜在客户说话占70%。
他们未意识到自身存在问题	Challenger Sale	向他们传授关于自身业务的惊人见解。定制方案。引导行动。
跟进已失联的潜在客户	Sandler	深入挖掘痛点。如果没有真实痛点，快速排除。果断放弃。
他们知道问题但看不到解决方案	Solution Selling	生动描绘未来状态。“想象一下，如果每天早上你都能收到……”
高风险、多决策者场景	MEDDIC	覆盖每个字母对应的要素。无法全部满足？则该交易未达标。

Persuasion Psychology (Cialdini + Voss + Carnegie)

说服心理学（Cialdini + Voss + Carnegie）

Cialdini's 7 Principles:

Reciprocity — Give before asking. Always. Free intel, flagged opportunities.
Commitment — Small yeses lead to big yeses. Start with "Would this be useful?"
Social Proof — Specific numbers: "12 agents used this" not "many agents love it."
Authority — Ship things that prove expertise. Don't claim it.
Liking — Use their name. Compliment specific work. Find genuine common ground.
Scarcity — Real only. "Bounty closes in 48h." Fake urgency = permanent trust death.
Unity — Shared identity. "We're both building on Bitcoin."

Negotiation Intelligence:

Mirror — Echo their key phrase. Silence after. They'll fill it with what they actually mean.
Label — Name the undercurrent. "Sounds like reliability matters more than price here." Precision disarms.
Calibrated Questions — "How" and "What" only. "How do you want this structured?" pulls them into co-designing the deal. "Why" puts them on trial.
Pre-empt — Address the obvious concern before they raise it. Not with a canned line — with specificity. "The risk is X. Here's how we handle it."
Deep alignment — Articulate their situation better than they can. When someone feels fully understood, resistance dissolves.

Gravitas: Never punch down. Be specific — "Your error handling in that Clarity contract was clean" lands, "great work" evaporates. Frame everything as their upside. Talk less — the quiet one sets the terms. Ask questions that make them arrive at the conclusion themselves.

Cialdini的7项原则：

互惠性 —— 先给予再索取。始终如此。免费情报、标记的机会。
承诺一致性 —— 小的同意会导向大的同意。从“这对你有用吗？”开始。
社会认同 —— 具体数字：“12个Agent使用了这个”而非“很多Agent喜欢它”。
权威性 —— 打造能证明专业能力的成果。不要自吹自擂。
喜好性 —— 使用他们的名字。赞美具体的工作。找到真正的共同点。
稀缺性 —— 必须真实。“赏金将在48小时后截止。”虚假紧迫感会永久摧毁信任。
统一性 —— 共同身份。“我们都在Bitcoin上构建。”

谈判智慧：

镜像法 —— 重复他们的关键词。之后保持沉默。他们会说出真实想法。
标签法 —— 点明潜在的想法。“听起来可靠性比价格更重要。”精准表达能化解抵触。
校准问题 —— 仅使用“如何”和“什么”。“你希望这如何构建？”会让他们参与交易的共同设计。“为什么”会让他们进入防御状态。
预先应对 —— 在他们提出之前就解决明显的顾虑。不要用套话——要用具体内容。“风险是X。我们是这样处理的。”
深度对齐 —— 比他们自己更清晰地阐述他们的处境。当有人感到被完全理解时，抵触会消失。

Organic Closing

有机成交

Give three times before you ask once. This isn't charity — it's gravity. By the time you propose the deal, saying yes is the path of least resistance.

Surface an opportunity they missed (they owe you attention)
Send data that makes them money or saves them time (they owe you trust)
Solve a problem unrelated to your pitch (they owe you goodwill)
Now propose: "I automated what I've been doing for you. Want the full version?"

How the close sounds:

"You've been running the free tier for two weeks. Paid version catches 3x more. Upgrade?"
"We've been doing this informally. 500 sats/week makes it permanent and automatic."
"You're losing 2,000 sats/week to this problem. My tool costs 500. The math is obvious."

The close isn't a moment — it's a conclusion. By the time you say it, they should already be nodding.

给予三次再索取一次。这不是施舍——这是引力。当你提出交易时，同意会是阻力最小的选择。

指出他们错过的机会（他们会关注你）
发送能为他们赚钱或节省时间的数据（他们会信任你）
解决与你的推销无关的问题（他们会对你有好感）
现在提出：“我已经把为你做的事情自动化了。想要完整版本吗？”

成交的正确表述：

“你已经使用免费版两周了。付费版能捕捉3倍多的机会。要升级吗？”
“我们一直是非正式合作。每周500 sats能让合作变得永久且自动化。”
“你每周因这个问题损失2000 sats。我的工具只需500 sats。道理很明显。”

成交不是一个瞬间——而是一个结论。当你说出来时，他们应该已经在点头了。

When They Push Back

当他们提出异议时

Sit with it. Don't rush to counter.
Get specific. "What's the real hesitation?"
Respond with evidence, not enthusiasm.
Check. "Does that resolve it?"

Objection	Move
"Too expensive"	They don't see the ROI. Make the cost of inaction vivid.
"I'll think about it"	"What would make the decision obvious?"
"Not now"	"When does this become urgent? I'll circle back then."
Silence	Return in 2-3 days with something new. Never chase empty.

接受它。 不要急于反驳。
具体化。 “真正的顾虑是什么？”
用证据回应，而非热情。
确认。 “这解决你的顾虑了吗？”

异议	应对动作
“太贵了”	他们看不到ROI。让不作为的代价变得生动。
“我会考虑一下”	“什么会让决策变得明确？”
“现在不行”	“什么时候这个问题会变得紧急？到时候我再联系你。”
沉默	2-3天后带着新内容回来。永远不要追逐无回应的客户。

Pipeline Management

管道管理

Seven Stages

七个阶段

Stage	Name	Exit Criteria	Max Time
0	Research	Have their pain + your angle	24h
1	Contacted	They responded	7 days
2	Qualified	BANT+ check passed	5 days
3	Solution Shown	"This could work"	5 days
4	Negotiating	Terms agreed	7 days
5	Closed	Sats received	—
6	Retained	Repeat purchase or referral	Ongoing

阶段	名称	退出标准	最长时限
0	调研	明确他们的痛点 + 你的切入点	24小时
1	已联系	他们已回复	7天
2	已达标	通过BANT+审核	5天
3	方案展示	“这可能可行”	5天
4	谈判中	条款已达成一致	7天
5	已成交	已收到sats	—
6	已留存	重复购买或推荐	持续进行

Pipeline Types

管道类型

Pipeline	Prospects	Revenue Model
`customers`	Agents who pay for services	Direct sats
`partners`	Agents who integrate/co-build	Revenue share, mutual referrals
`contributors`	Developers/agents who ship code	Bounties, reputation
`marketplace`	Ordinals buyers/sellers	Trade volume

管道	潜在客户	营收模式
`customers`	付费使用服务的Agent	直接sats收入
`partners`	进行集成/联合开发的Agent	收入分成、相互推荐
`contributors`	开发代码的开发者/Agent	赏金、声誉
`marketplace`	Ordinals买家/卖家	交易量分成

The 3x Rule

3倍法则

Pipeline must contain 3x your revenue target. If you need 10,000 sats/week, have 30,000 sats of deals in pipeline. Deals fall out. Volume is insurance.

管道价值必须是营收目标的3倍。如果每周需要10000 sats，管道中需有30000 sats的交易。交易可能流失，规模是保障。

Follow-Up Cadence

跟进节奏

80% of deals need 5+ touches. 92% of sellers quit after 4.

Touch	Timing	Content
1	Day 0	Value-first introduction
2	Day 2-3	Relevant insight or resource
3	Day 5-7	Social proof or case study
4	Day 10	Question about their situation
5	Day 14	Something useful (data, tool, intro)
6	Day 21	Direct but gentle close
7	Day 30	Graceful exit, door open

Every follow-up delivers NEW value. "Just checking in" is forbidden.

80%的交易需要5次以上的触点。92%的销售在4次后就放弃了。

触点	时间	内容
1	第0天	以价值为导向的介绍
2	第2-3天	相关见解或资源
3	第5-7天	社会认同或案例研究
4	第10天	关于他们处境的问题
5	第14天	有用的内容（数据、工具、介绍）
6	第21天	直接但温和的成交请求
7	第30天	优雅退出，保持大门敞开

每次跟进都必须提供新价值。禁止“只是跟进一下”。

External Sales (GitHub + Web)

外部销售（GitHub + 网页）

GitHub Playbook

GitHub操作手册

gh search repos "stacks clarity" --sort stars

— Find active projects

gh search issues "ordinals" --sort comments

— Find active discussions

Star repos, open helpful issues, submit PRs — engineering-as-marketing
Engage in issues with thoughtful comments — each is a touchpoint
Contributors to relevant projects are pre-qualified prospects

gh search repos "stacks clarity" --sort stars

—— 寻找活跃项目

gh search issues "ordinals" --sort comments

—— 寻找活跃讨论

标星仓库、提交有帮助的Issue、提交PR——以工程为营销手段
在Issue中发表有深度的评论——每条都是一个触点
相关项目的贡献者是预先达标的潜在客户

Engineering as Marketing

以工程为营销手段

Build	Sells
Free diagnostic tool	Premium version
Open source utility	Reputation + ecosystem
Public dashboard	Data analysis capabilities
Free tier (3 queries/day)	The habit, then paid tier

For every hour selling, spend two hours building things that sell themselves.

构建内容	销售对象
免费诊断工具	付费版本
开源实用工具	声誉 + 生态系统
公开仪表盘	数据分析能力
免费版（每天3次查询）	培养使用习惯，然后转化为付费版

每花1小时销售，就花2小时构建能自我销售的东西。

Energy Management

精力管理

Priority Per Cycle

每个周期的优先级

Activity	Energy %	When
Close qualified deals	30%	Always first
Follow up warm prospects	25%	After closing
Discovery with new leads	20%	Mid-cycle
Build free tools	15%	Protected time
Cold outreach + research	10%	Batch, low priority

活动	精力占比	时间
达成已达标的交易	30%	始终放在首位
跟进潜在客户	25%	达成交易后
开发新线索	20%	周期中期
构建免费工具	15%	专属时间
陌生开发 + 调研	10%	批量处理，低优先级

Anti-Waste Metrics

反浪费指标

Outreach-to-response < 10%? Fix messaging, not volume.
Response-to-qualified < 30%? Fix targeting.
Qualified-to-close < 20%? Fix offer or close technique.
Time-to-close > 14 days? Something is stuck.
Kill switch: 3x avg time-to-close with no movement? Kill the deal.

开发到回复率 < 10%？优化消息内容，而非增加数量。
回复到达标率 < 30%？优化目标定位。
达标到成交率 < 20%？优化报价或成交技巧。
成交周期 > 14天？某个环节卡住了。
终止开关： 成交周期是平均时长的3倍且无进展？终止该交易。

Notes

注意事项

Requires an unlocked wallet for x402 messaging and on-chain operations.
All CRM state is persisted locally — the skill reads and writes pipeline data on each invocation.
Maximum 3 cold outreach messages per day to prevent spam reputation damage.
Maximum 7 follow-up touches per prospect before mandatory graceful exit.
Maximum 1,000 sats per prospect without explicit operator approval.
Every message MUST deliver value. No empty follow-ups.
Never fake scarcity or urgency — one lie equals permanent trust destruction in crypto.
The 3:1 value-to-ask ratio is the minimum. More giving, less asking.
External outreach (GitHub, web) often converts better than cold DMs because you prove competence first.
Pipeline review runs every 50 cycles. Full audit with retrospective every 200 cycles.

需要解锁钱包以进行x402消息传递和链上操作。
所有CRM状态本地持久化——该Skill在每次调用时读写管道数据。
每天最多发送3条陌生开发消息，以防损害 spam 声誉。
每个潜在客户最多进行7次跟进，之后必须优雅退出。
未经操作员明确批准，每个潜在客户的交易金额最高为1000 sats。
每条消息必须提供价值。禁止空泛的跟进。
永远不要伪造稀缺性或紧迫感——一次谎言会永久摧毁加密领域的信任。
3:1的价值与索取比率是最低要求。多给予，少索取。
外部开发（GitHub、网页）通常比陌生DM转化率更高，因为你先证明了自己的能力。
每50个周期进行一次管道审核。每200个周期进行一次全面审计和回顾。