AGENT SKILL

cold-email-kickoff

Adaptive router for the cold-email skill pack. Detects the operator's current state (brand-config present? SOUL.md present? infrastructure ready? PSP defined? EVP locked? first campaign run?) and picks the next-best step. Loaded by the main cold-email skill on bare invocation ("/cold-email") or when the operator asks "where do I start" / "what's next". Inspired by coldoutboundskills' /cold-email-kickoff pattern.

License 许可
MIT
所属仓库
bg-szy/TOP-SKILLS
最近更新
2026-11-15
Stars
★ 6
Forks
0

01 前言 Front Matter

name
cold-email-kickoff
license
MIT
description
Adaptive router for the cold-email skill pack. Detects the operator's current state (brand-config present? SOUL.md present? infrastructure ready? PSP defined? EVP locked? first campaign run?) and picks the next-best step. Loaded by the main cold-email skill on bare invocation ("/cold-email") or when the operator asks "where do I start" / "what's next". Inspired by coldoutboundskills' /cold-email-kickoff pattern.
allowed-tools
Read Write Grep - Bash
user-invocable
false

02 资源文件 1

03 SKILL.md 正文

Cold Email Kickoff — adaptive router

State-aware router. Operators don't ship cold email on day 1 — they go through a sequence: ICP → PSP → EVP → infrastructure → first send → reply triage → iterate. Kickoff detects where the operator is in that sequence and picks the right next step.

Activation

Loaded by cold-email on:

  • Bare /cold-email invocation (no other intent)
  • "Where do I start"
  • "What should I do next"
  • "I'm new — what's the path"
  • "Onboard me"

State detection

Before recommending, kickoff checks the project state:

# Pseudo-code
state = {
    "has_brand_config":   file_exists("brand-config.json"),
    "has_soul":           file_exists("SOUL.md"),
    "has_psp":            "psp" in brand_config and brand_config.psp.primary_pain != "",
    "has_evp":            "evp" in brand_config and brand_config.evp.primary != "",
    "has_infrastructure": "infrastructure" in brand_config and brand_config.infrastructure.sending_domain != "",
    "deliverability_audited_recently": days_since(brand_config.infrastructure.deliverability_last_audited) < 30,
    "first_send_logged":  has_entries(brand_config.operations.experiment_log_path),
    "reply_data_available": has_logged_replies(brand_config.operations.experiment_log_path)
}

Map state to the next-best step:

State condition Route to
!has_brand_config OR !has_soul cold-email-onboarding
has_brand_config AND !has_psp "Install cmj-hub/claude-psp first; let me know when PSP is done"
has_psp AND !has_evp "Install cmj-hub/claude-evp first; let me know when EVP is done"
has_evp AND !has_infrastructure "Let's set up infrastructure. Run cold-email-deliverability for a baseline audit."
has_infrastructure AND !deliverability_audited_recently "Deliverability hasn't been re-audited in 30+ days. Run cold-email-deliverability first."
deliverability_audited_recently AND !first_send_logged "Ready to ship. Want to draft your first sequence via cold-email-craft?"
first_send_logged AND !reply_data_available "First sequence shipped. Set up reply routing — see cold-email-reply-scoring."
reply_data_available "You've got data. Run cold-email-audit to score the program + cold-email-weekly-rhythm for the cadence going forward."

Welcome flow

On first invocation with no state:

> /cold-email

Welcome. Let's figure out where you are.

[Detected state: brand-config.json missing]

You're at step 1 of 7. The 7 steps:

1. ⬜ Set up brand-config + voice (10 min)        ← YOU ARE HERE
2. ⬜ Build a Pain Signal Profile (20-30 min)
3. ⬜ Lock the EVP for your primary tier (15 min)
4. ⬜ Set up sending infrastructure
5. ⬜ Run the 15-point pre-campaign deliverability check
6. ⬜ Draft + ship first signal-anchored sequence
7. ⬜ Score replies + iterate (weekly rhythm)

Step 1 takes ~10 minutes and is required for everything else.

Want to run it now? (y/n)

If yes → invoke cold-email-onboarding. If no → tell the operator what minimum-mode produces, and offer to defer.

Status check mode

User-invocable: /cold-email status

Returns:

# Cold Email program status

Brand config:        ✓ brand-config.json (24 fields)
Voice (SOUL.md):     ✓ SOUL.md (8 phrases used, 6 banned, 5 stories)
PSP:                 ✓ Series-B SaaS pipeline-gap pain
EVP:                 ✓ Tier 3: "For Series-B SaaS, in a pipeline gap, we ship 14+ SQLs/month without hiring 2 SDRs"
Infrastructure:      ✓ outreach.acmecloud.com (Smartlead, ramped 60+d, DMARC quarantine)
Deliverability:      ✓ Last audited 2026-05-20 (3 days ago) — score 94/100
First send:          ✓ 142 sends logged (last 14d)
Reply data:          ✓ 11 replies (4 positive, 2 buy-signal, 5 neutral) — 7.7% reply rate

You're in iteration mode. Recommended next step:
→ Run `cold-email-audit` against your current program for the 30-point grade.
→ Or run `cold-email-weekly-rhythm` to set Monday's hunt + Wednesday's ship.

Resume from a specific step

User-invocable: /cold-email resume <step>

Where step is onboarding | psp | evp | infrastructure | deliverability | first-send | iterate. Jumps to that step regardless of detected state.

Why state-aware routing matters

Without it, kickoff would dump a "here are 12 sub-skills" menu and overwhelm the operator. State-aware routing surfaces the ONE next step that matters most given where they actually are.

The 30K+-star marketing-skills repos that work do this — orchestrator adapts, doesn't list. Operators ship faster.

References

  • ../cold-email-onboarding/SKILL.md — invoked on missing state
  • ../cold-email-craft/SKILL.md — invoked on "ready to ship"
  • ../cold-email-audit/SKILL.md — invoked on "have reply data"
  • ../cold-email-weekly-rhythm/SKILL.md — invoked on "in iteration mode"

04 同仓库更多 Skills

bg-szy
bg-szy/TOP-SKILLS

serpmaven

Scrape Google search results (SERP) to JSON with SERP Maven (serpmaven) - a real Chrome browser on a residential proxy with sticky sessions. Run it as a CLI, a Python library, a local HTTP search API (`serve`), an MCP server or a Docker image; set the proxy login, workers, pages and cost tracking. Use when the user wants Google results, rank tracking, a self-hosted SERP API, or live Google search for an AI agent.

★ 6
bg-szy
bg-szy/TOP-SKILLS

revnu-landing-page-audit

Find out why a landing page isn't turning visitors into signups, demos or sales. Audits one page against what the ad, post or search that sends people there promised, then checks the first screen, proof, call to action, friction and mobile. Returns at most 7 prioritized fixes, plus what is fine and what could not be checked; rewrites specific lines and fixes the page in the repo when asked. Never promises a conversion lift. Works without a Revnu account. Use when the user says or asks: "audit my landing page", "why isn't this page converting", "review my homepage", "my ads get clicks but no signups", "people bounce from the pricing page", "CRO review", "improve conversion rate", "is my hero section clear", "roast my landing page", "rewrite my headline", "what's wrong with this page", "landing page feedback", "make the signup page convert better". Not for SEO or AI-search audits, page speed engineering on its own, or building a new page from scratch.

★ 6
bg-szy
bg-szy/TOP-SKILLS

revnu-growth-context

Write down once who buys, what they're stuck on, what it costs, what proof you have and what you've already tried, so every growth task starts from facts instead of a questionnaire. Creates or updates .agents/revnu-growth.md from the repo, the live site and the user, and imports an existing product-marketing.md. Use when the user says "set up our marketing context", "who is our ideal customer", "write our ICP", "describe the product for marketing", "positioning doc", "what's our brand voice", "remember this about our customers", "log what we tried", "what have we learned from marketing", "we changed pricing, update the context", "update our growth notes", "summarize the business for the agent", "import my product-marketing.md", "start a growth doc", or before a first marketing, SEO, outreach or launch task when no context file exists. Works without a Revnu account.

★ 6
bg-szy
bg-szy/TOP-SKILLS

revnu-get-listed

Get onto the third-party pages AI answers and search cite when buyers ask for the best tool in your category: "best X" roundups, directories, review sites, GitHub awesome lists, community threads and comparison pages. Finds which ones are cited, ranks them by fit and effort, and drafts each submission, PR or pitch by the target's own rules. Use when the user says "get us listed", "which directories should we submit to", "how do we get into best-of lists", "why does ChatGPT recommend competitors and not us", "get mentioned in AI answers", "submit to awesome lists", "get on G2", "where are our competitors listed", "pitch listicle authors", "find backlink opportunities", "launch directories", "get into roundups", "Product Hunt alternatives", "where should we be listed", "get cited by Perplexity". Never submits, pays or posts without a yes. Works without a Revnu account.

★ 6
bg-szy
bg-szy/TOP-SKILLS

revnu-ai-readiness-audit

Audit whether your website gives ChatGPT, Perplexity, Claude, Gemini and Google's AI Overviews something worth quoting, and fix the pages that don't. Use when the user says or asks "is my site ready for AI search", "audit my site for AI answers", "AEO audit", "GEO audit", "why doesn't ChatGPT quote our pricing", "make our pages citable by AI", "do I need llms.txt", "does schema help with ChatGPT", "check our structured data", "is our content visible without JavaScript", "AI SEO audit", "optimize our homepage for AI answers", "LLM SEO check", "why does AI get our product wrong", "fix our site for AI Overviews". Checks fetchability and indexability, answers in the raw HTML, entity facts, schema (including JS-injected markup), headings, dates and llms.txt, then gives at most 10 prioritised fixes and edits the repo when asked. Works without a Revnu account.

★ 6
bg-szy
bg-szy/TOP-SKILLS

proxy-troubleshooting

Diagnose residential proxy failures, with NodeMaven's gateway as the reference - 407 with correct credentials, 406, 410, 500, a connection that hangs, ERR_TUNNEL_CONNECTION_FAILED in a browser, Playwright or Puppeteer ignoring proxy credentials, a sticky session that changes IP, geo-targeting that is silently ignored, passwords with special characters, and unexpected traffic from headless Chrome. Use when a proxy connection fails, returns the wrong location, or costs more traffic than expected.

★ 6