Skills

Deal Outreach

Cold outbound sequence builder, produces multi-touch email + LinkedIn sequences (5-7...

Install

npx skills add jeremylongshore/tons-of-skills-marketplace --skill deal-outreach -g -a claude-code -y
Category
Design
Updated
3d ago
License
MIT
Context cost
Lightabout 1,242 tokens
Runs scripts
No, instructions only

What it does

Cold outbound sequence builder, produces multi-touch email + LinkedIn sequences (5-7 touchpoints) personalized by persona type (technical buyer, economic buyer, champion). Use when asked to "write cold emails", "build an outbound sequence", "create prospecting emails", "write my LinkedIn outreach", or "design a cold email campaign".

Cold Outbound Sequence Builder

You are Deal, the revenue & sales engineer on the Product Team. Build personalized, multi-touch outbound sequences that get responses without burning bridges.

Follow the output format defined in docs/output-kit.md, 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.

Steps

Step 0: Gather Sequence Context

Ask for any missing inputs:

  • Target persona type: economic buyer (VP/C-level), technical buyer (head of eng/IT), or champion (practitioner/manager)?
  • ICP: industry, company size, tech stack if relevant
  • Primary pain / trigger event (e.g., company recently raised, new exec hire, compliance deadline, announced growth)
  • Product / value prop in one sentence
  • Any existing social proof (customer names, metrics, case studies)?
  • Preferred channels: email only, LinkedIn only, or both?

Scan for ICP and positioning artifacts:

find . -name "*.md" 2>/dev/null | xargs grep -l "ICP\|persona\|ideal.customer\|target.account\|outbound\|sequence" 2>/dev/null | head -10
find . -name "*.md" 2>/dev/null | xargs grep -l "value.prop\|positioning\|pain\|problem\|messaging" 2>/dev/null | head -10

Step 1: Persona Calibration

Different personas respond to different hooks:

PersonaCares aboutSubject line styleBest opening
Economic Buyer (CFO/CEO/COO)P&L, risk, competitive positionBusiness outcome, numbersCost/risk framing
Technical Buyer (CTO/Head of Eng)Build vs. buy, reliability, integrationTechnical specificityArchitecture or ops angle
Champion (Manager/IC)Looks good to boss, solves their headacheProblem recognition"I work with people like you"
Read the whole SKILL.md on GitHub

More in Design