deal-outreach
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".
What this skill does
# 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: ```bash 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: | Persona | Cares about | Subject line style | Best opening | | --------------------------------- | ----------------------------------------- | ------------------------- | ----------------------------- | | Economic Buyer (CFO/CEO/COO) | P&L, risk, competitive position | Business outcome, numbers | Cost/risk framing | | Technical Buyer (CTO/Head of Eng) | Build vs. buy, reliability, integration | Technical specificity | Architecture or ops angle | | Champion (Manager/IC) | Looks good to boss, solves their headache | Problem recognition | "I work with people like you" | ### Step 2: Sequence Architecture Use a 6-touch sequence with a clear arc: | Touch | Channel | Timing | Goal | | ----- | -------- | ------ | --------------------------------------- | | 1 | Email | Day 0 | Pattern interrupt — get them to read | | 2 | LinkedIn | Day 2 | Warm the name, connect request | | 3 | Email | Day 5 | Different angle / proof point | | 4 | LinkedIn | Day 8 | Message if connected | | 5 | Email | Day 12 | Case study / social proof | | 6 | Email | Day 18 | Breakup — low pressure, leave door open | ### Step 3: Write the Sequence Produce each touchpoint in full. Apply the persona calibration from Step 1. **Rules for every touch:** - Subject line: <7 words, no punctuation spam, no "Re:" tricks - Opening line: specific to them or their company — never generic - Body: 3-5 sentences max per email. One idea per touch. - CTA: one action only. "15 minutes?" or "Worth a quick chat?" not "Schedule a demo at your convenience using this link" - Never attach anything in the first 3 touches - No "Hope this finds you well", no "I wanted to reach out", no "synergy" ``` ## Touch 1 — Email (Day 0) Subject: [subject line] --- [Opening — specific observation about them or their company] [One sentence: what you do and for whom] [One sentence: the outcome, with a number if you have one] [CTA — one question] [Name] --- ## Touch 2 — LinkedIn (Day 2) Connection request note (300 char max): [Brief, non-salesy. Reference their work, not your product.] ## Touch 3 — Email (Day 5) Subject: [different angle subject] --- [Different hook — competitor angle, or industry trend, or "quick question"] [One proof point: customer name + outcome] [CTA] [Name] --- ## Touch 4 — LinkedIn Message (Day 8) [If connected: 2-3 sentences. Reference connection context. Soft CTA.] ## Touch 5 — Email (Day 12) Subject: [case study or social proof angle] --- [Open with a customer story in 1 sentence: "[Similar company] used us to [outcome]."] [Ask if that pattern applies to them] [CTA] [Name] --- ## Touch 6 — Breakup Email (Day 18) Subject: [Closing the loop / Should I stop?] --- [Acknowledge: you've reached out a few times, understand if timing isn't right] [Leave a door open: one sentence on the value if they ever reconsider] [No CTA — just permission to reply if interested] [Name] --- ``` ### Step 4: Timing and Sending Notes - Send emails Tuesday-Thursday, 8-10am or 3-5pm recipient timezone - LinkedIn connection requests: Monday or Wednesday - Never send touch 6 if they opened 3+ emails without replying — they're reading, add a touch 5.5 instead - Personalization tokens to add per prospect: `[[first_name]]`, `[[company]]`, `[[trigger_event]]` ## Delivery Output all 6 touches as ready-to-load copy. Flag any personalization tokens that require manual fill. If output exceeds 40 lines, delegate to /atlas-report.
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".