菜单
Child skill for classifying cold outreach replies into a 12-class taxonomy, routing objections through a 7-route table, reviving silence with numbered forks, and answering within SLA so trust is preserved after a recipient responds or goes quiet.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/Wolverine971/buildos-platform --skill cold-email-reply-os命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Query and manage the BuildOS Supabase database. Use for debugging data issues, checking users, LLM usage, queue jobs, schema questions, or admin database operations with safety checks.
Build animations in React Native and Expo, making the decisions in the order that determines whether they feel right — should it animate, which thread it runs on, which properties, spring or timing, how the gesture hands off, how it degrades. Writes the implementation with Reanimated, Gesture Handler, Expo Router and expo-haptics. Use when animating anything in an Expo app, adding gestures, sheets, screen transitions, press feedback or haptics, or fixing motion that stutters on device. For web animation use `animate`.
Build an animation from scratch, making the decisions in the order that determines whether it feels right — should it animate at all, what purpose, which tool, which properties, which curve and duration, how it interrupts, how it exits. Writes the implementation. Use when asked to animate something, add motion, make a component feel alive, or build a transition. For critiquing existing motion use review-animations; for auditing a whole codebase use improve-animations.
基于 SOC 职业分类
正在显示 SKILL.md
| name | Cold Email Reply OS |
| description | Child skill for classifying cold outreach replies into a 12-class taxonomy, routing objections through a 7-route table, reviving silence with numbered forks, and answering within SLA so trust is preserved after a recipient responds or goes quiet. |
| skill_type | strategy |
| altitude | domain |
| activation | progressive |
| parent_id | cold_email_engagement_first_outreach |
| depth | 1 |
| preserve_markdown | true |
| legacy_paths | ["cold_email_outreach.reply_os","cold_email_outreach.objection_handling"] |
| reference_modules | [{"id":"cold_email_reply_os.objection_routes","name":"Objection Route Table","summary":"7-objection route table with labels and calibrated questions, Gong 7-step async adaptation, and the objection-bank template structure (acknowledge -> label -> one contrast/artifact -> smallest calibrated question).","when_to_load":["When the reply is an objection, skepticism, competitor-chosen, or a send-info brushoff."],"path":"references/objection-route-table.md","visibility":"internal"},{"id":"cold_email_reply_os.fork_library","name":"Numbered Fork Library","summary":"Three named forks (qualification, ghosted-thread, Hail Mary) with full text, fork discipline rules, and silence-revival cadence by mode.","when_to_load":["When silence revival or a numbered fork is the chosen move (workflow steps 2, 7)."],"path":"references/numbered-fork-library.md","visibility":"internal"},{"id":"cold_email_reply_os.tactical_empathy_routes","name":"Tactical Empathy Routes","summary":"Route table and label -> calibrated question patterns for objections, silence, skepticism, angry replies, and ambiguous replies.","when_to_load":["When a reply is skeptical, tense, ambiguous, negative, silent, or objection-heavy and you need label and question phrasing."],"path":"references/tactical-empathy-routes.md","visibility":"internal"}] |
| path | apps/web/src/lib/services/agentic-chat/tools/skills/definitions/cold_email_reply_os/SKILL.md |
Use this child skill after sending, when a reply arrives, a thread goes quiet, or objections need routing. The discipline this skill enforces is classify first: every reply gets a taxonomy class before any draft, route, or fork. A route without a taxonomy class is not a route. Replies are scarce trust signals — the north star is qualified conversations started per unit of market trust consumed.
This is a strategy skill at domain altitude, a child under cold_email_engagement_first_outreach. It decides how to classify and route each reply rather than running a fixed runbook: the 12-class taxonomy and SLA data it reasons over are the unconditional lookup grounding in Knowledge, while the conditional route/fork/empathy phrasing loads from its reference modules.
The goal of the email is a response. The goal of reply handling is to preserve momentum without forcing the wrong next step. Replies are scarce trust signals — route them the same day. Silence is the only dead state.
Classify before you draft anything. A route without a taxonomy class is not a route.
For high-intent replies:
Do not leave high-intent replies in the inbox overnight when the campaign depends on booked calls.
Use when the buyer has shown clear interest and the sales motion supports calls.
Safe frame:
Makes sense. I can send the snapshot first.
If it looks relevant, I have [time 1] or [time 2] open tomorrow to walk through what I found.
Avoid:
Once someone agrees to a meeting, follow up until it is booked or they decline.
Good follow-up assets:
Avoid generic "checking in."
Use a short dignified close:
Understood. I will not follow up.
Do not defend, debate, explain intent, or ask one more question after an opt-out. Suppress the address.
cold_email_reply_os.objection_routes and pick the matching route row. Silence or revival → load cold_email_reply_os.fork_library and pick one of the three named forks. For label and calibrated-question phrasing on tense or ambiguous replies, load cold_email_reply_os.tactical_empathy_routes.cold_email_icp_signal_design (see Routing); an opt-out suppresses the address immediately.cold_email_reply_os.fork_library — one fork per thread, ever — and set the revival cadence by mode from the fork library.cold_email_learning_review (buyer language feeds the learning review).Who owns what when this skill hands off. Reply handling stays inside this skill; two branches escalate to sibling skills, and the conditional phrasing loads from this skill's own reference modules.
| Trigger (Procedure step) | Intent (what) | Owner (who) |
|---|---|---|
| Left-company auto-reply (step 6) | Fire the trigger workflow; treat both trigger events | cold_email_icp_signal_design |
| Buyer-language log (step 8) | Objection language verbatim feeds the learning loop | cold_email_learning_review |
| Objection / skeptical / competitor / send-info-brushoff (step 2) | Route row + label + calibrated question | cold_email_reply_os.objection_routes, cold_email_reply_os.tactical_empathy_routes (reference modules) |
| Silence / revival / numbered fork (steps 2, 7) | Named fork + revival cadence | cold_email_reply_os.fork_library (reference module) |
A "left company" auto-reply is not a dead address — it is two trigger events (Elias): the departed person is landing somewhere new with fresh budget and old pain, and the old seat has a successor in their decision window. Hand both to cold_email_icp_signal_design as trigger-event inputs; do not handle them inside the reply thread.
| # | Class | Detection cues | Intent |
|---|---|---|---|
| 1 | Yes / interested | "send it," "tell me more," asks a question about the offer | High |
| 2 | Send info | "send me something," "what's the pricing" | Medium-high |
| 3 | Numbered response | replies "1"/"2"/"3" to a fork | Per option |
| 4 | Not now / timing | "next quarter," "after [event]" | Medium (timeline data — Moesta) |
| 5 | Already solved / competitor | names incumbent or "we're covered" | Low-medium (objection-discovery value — Close Hail Mary) |
| 6 | Objection (budget / priority / risk / switching) | substantive pushback | Medium |
| 7 | Skeptical | "does this actually…," challenge to claim | Medium (serious buyers get critical — Gong: negative sentiment increases toward purchase) |
| 8 | Wrong person / referral | "talk to X," "not my area" | Routing value (Elias: a referral target is warmer than a cold name) |
| 9 | Compliment-no-action | "great email!" with no movement | Weak evidence (Mom Test: tag compliments weak) |
| 10 | Angry / opt-out | "stop emailing me," unsubscribe | Stop |
| 11 | Auto-reply / OOO / left-company | bounce text | "Left company" = trigger event for the ICP child (Elias bounce surface) |
| 12 | Ambiguous | unclassifiable one-liner | Ask one calibrated question; do not assume |
Speed rationale: replies are scarce trust signals; route same day. Do not leave high-intent replies overnight when the motion depends on calls. Do-not-import note: Hormozi's 391% speed-to-contact stat is inbound list-email territory — never cite it as a cold-email SLA fact.
| Reply class | Owner | First response SLA | Notes |
|---|---|---|---|
| Yes / interested, numbered 1 | Sender (human) | Same business day; within 1–2h if call motion | Keep artifact promise before any meeting push |
| Send info | Sender or assistant | Same business day | Send the promised artifact, never a brochure |
| Objection / skeptical | Sender (human — judgment required) | Within 1 business day | Use the objection route table (load cold_email_reply_os.objection_routes) |
| Wrong person / referral | Sender | Within 1 business day | Thank, ask routing question, log new contact |
| Not now | Sender | Within 2 business days | Ask permission for a specific future touch; calendar it (Close follow-up guide: "I'll put that in my calendar and ping them in 14 days") |
| Angry / opt-out | Sender | Same day | Two lines max, confirm stop, suppress address |
| Left-company auto-reply | System → ICP child | n/a | Fire trigger workflow (Elias) |
| Ambiguous | Sender | 1 business day | One calibrated question only |
Compliment-no-action (class 9) and OOO auto-replies carry no SLA: tag the compliment as weak evidence and move on; resume cadence after an OOO return date.
Condensed from a full classify-and-respond run on a "send me some info" reply to a strategic first touch; the input thread is in evals.md Task 1. Match this shape: class before draft, route row named, one CTA, log line at the end.
Input: First touch (strategic, 8 hand-picked accounts) offered Dana, VP RevOps, a 2-page pipeline-review teardown ("Want me to send the Meridian-relevant version?"). Her reply: "Thanks Alex. Sounds interesting — send me some info and I'll take a look when I get a chance." The sender's instinct: send the company deck and ask if she's free Thursday or Friday for a call.
1. Classification (before any draft): Class 2 — Send info ("send me some info" is the detection cue). Intent: medium-high. Not class 1 (yes/interested) — "when I get a chance" is deferral language, so handle it as the send-me-info-as-brushoff pattern from the objection route table. A route without a taxonomy class is not a route; the class came first.
2. Owner + SLA: Sender or assistant, same business day — send-info is a same-day class. Reply while the thread is warm.
3. Route (objection route table, brushoff row): No label needed. Send the real artifact + one-line fork: active vs. polite-no. Two corrections to the sender's plan, by rule:
4. Response draft (artifact + one calibrated question, what/how only, never "why"):
Here it is — the 2-page teardown, with the Meridian pod-structure notes on page 2.
No deck and no drip sequence behind this. One question so I don't clutter your
inbox: should I close the loop after this, or is the noisy-pipeline-review
problem still live this quarter?
— Alex
The question is the route row's active-vs-polite-no fork: either answer is useful, and "close the loop" gives her a dignified no.
5. Stop / follow-up rule: If silence follows the artifact, strategic cadence allows up to 4 touches over ~7–8 days, then stop. The ghosted-thread numbered fork stays in reserve — one fork per thread, ever — so it is not spent here while the thread is live.
6. Buyer-language log (for cold_email_learning_review): class 2 send-info-brushoff · route: artifact + active-vs-polite-no fork · verbatim: "Sounds interesting — send me some info and I'll take a look when I get a chance." — deferral phrasing, no named pain; grade as weak evidence until behavior follows.
Output contract check: class ✓ intent ✓ route row named ✓ draft ✓ artifact ✓ owner/SLA ✓ stop rule ✓ log line ✓.
references/.docs/research/youtube-library/cold-email-children-enrichment-plan-2026-06-10.md and the draft references at docs/research/youtube-library/skill-drafts/cold-email-engagement-first-outreach/references/ (not available at runtime).