cold-outreach-skill_skill

Overview

This skill orchestrates Apollo, LinkedIn, YC Cold Outreach, and MachFive Cold Email into a single end-to-end B2B cold outreach pipeline. It runs from ICP definition and lead sourcing to enrichment, YC-guided message strategy, and generation-ready sequences with strict QA and safety gates. Use it when you need production-ready outreach assets and clear handoff instructions for external send systems.

How this skill works

The skill queries Apollo to build an ICP-constrained lead universe, pages until the target count or quality threshold, and normalizes records. It enriches leads with LinkedIn-supported context where available, applies the YC Cold Outreach framework to create a Problem→Solution→Proof→CTA brief, then calls MachFive Cold Email to generate multi-step sequences. Each sequence passes factuality, YC-rubric, and token-sanity checks before being marked approved or flagged for revision.

When to use it

• You need end-to-end lead sourcing, enrichment, and sequence generation for a B2B campaign.
• You require strict factuality and safety gates before sending outreach.
• You have required API keys (MATON_API_KEY, MACHFIVE_API_KEY) and a campaign context.
• You want ready-to-import JSON sequences for an external scheduler or ESP.
• You want concise, human-first messaging following YC outreach principles.

Best practices

• Provide a complete job context (offer, ICP fields, lead_count_target, campaign goal, proof points, tone, execution_mode).
• Resolve or supply MachFive campaign ID before requesting generation-ready sequences.
• Run draft-only first for review when any credential or campaign is missing.
• Do not ask the skill to invent personal posts or claims—keep personalization to verifiable context.
• Use batch generation for large lists and poll for list completion to ensure reliable exports.

Example use cases

• Generate 50 vetted CMO leads in Berlin SaaS, enrich them, and produce a 3-step email sequence per lead.
• Produce draft messaging strategies and sample emails when MACHFIVE_API_KEY is not available.
• Run a QA pass to flag sequences that contain ambiguous CTAs or unverified personalization.
• Export sequence JSON mapped to lead IDs for import into a scheduling tool with send-time recommendations.