Prospecting
coreyhaines31/marketingskills
When the user wants to find, qualify, and build a list of prospects to reach out to, across B2B SaaS, general B2B, or local small businesses.
When the user wants to design a multi-channel outbound sequence or cadence.
$ npx skills add TheCraigHewitt/skills --skill outbound-sequence -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install TheCraigHewitt/skills outbound-sequence --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/TheCraigHewitt/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/sales/outbound-sequence .claude/skills/outbound-sequence && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "outbound-sequence" agent skill from https://github.com/TheCraigHewitt/skills/tree/main/sales/outbound-sequence into .claude/skills/outbound-sequence/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "outbound-sequence", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/TheCraigHewitt/skills/tree/main/sales/outbound-sequenceType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add TheCraigHewitt/skills --skill outbound-sequence -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install TheCraigHewitt/skills outbound-sequence --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/TheCraigHewitt/skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/sales/outbound-sequence .agents/skills/outbound-sequence && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "outbound-sequence" agent skill from https://github.com/TheCraigHewitt/skills/tree/main/sales/outbound-sequence into .agents/skills/outbound-sequence/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "outbound-sequence", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add TheCraigHewitt/skills --skill outbound-sequence -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install TheCraigHewitt/skills outbound-sequence --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/TheCraigHewitt/skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/sales/outbound-sequence .cursor/skills/outbound-sequence && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "outbound-sequence" agent skill from https://github.com/TheCraigHewitt/skills/tree/main/sales/outbound-sequence into .cursor/skills/outbound-sequence/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "outbound-sequence", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/TheCraigHewitt/skills.git --path sales/outbound-sequence--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add TheCraigHewitt/skills --skill outbound-sequence -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install TheCraigHewitt/skills outbound-sequence --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/TheCraigHewitt/skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/sales/outbound-sequence .gemini/skills/outbound-sequence && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "outbound-sequence" agent skill from https://github.com/TheCraigHewitt/skills/tree/main/sales/outbound-sequence into .gemini/skills/outbound-sequence/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "outbound-sequence", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install TheCraigHewitt/skills outbound-sequenceInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add TheCraigHewitt/skills --skill outbound-sequence -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/TheCraigHewitt/skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/sales/outbound-sequence .github/skills/outbound-sequence && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "outbound-sequence" agent skill from https://github.com/TheCraigHewitt/skills/tree/main/sales/outbound-sequence into .github/skills/outbound-sequence/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "outbound-sequence", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add TheCraigHewitt/skills --skill outbound-sequence -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install TheCraigHewitt/skills outbound-sequence --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/TheCraigHewitt/skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/sales/outbound-sequence .opencode/skills/outbound-sequence && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "outbound-sequence" agent skill from https://github.com/TheCraigHewitt/skills/tree/main/sales/outbound-sequence into .opencode/skills/outbound-sequence/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "outbound-sequence", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
outbound-sequenceWhen the user wants to design a multi-channel outbound sequence or cadence.
Outbound Sequence is an agent skill from TheCraigHewitt/skills. When the user wants to design a multi-channel outbound sequence or cadence. Also use when the user says 'build me a sequence,' 'create a cadence,' 'how many touches,' 'what's the right sequence,' 'multi-channel outreach plan,' 'design my outbound,' 'how should I follow up,' 'SDR playbook,' 'outbound motion,' 'sales sequence,' 'follow-up strategy,' 'prospecting cadence,' or 'drip sequence.' For individual channel content, see cold-email, cold-call, linkedin-outreach, or direct-mail. For research before sequencing…
Its SKILL.md is about 6.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Sales & Support, covering Cold outreach. It works with LinkedIn. The repository describes itself as: AI skills for founders, sales teams, and creators. 47 skills across CEO, Sales, YouTube, and General categories. Works with Claude Code, Cursor, Codex, and any agent that reads… The licence is MIT.
7 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit fdbf39b. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Outbound Sequence loads about 6.3k tokens when it runs. Until then it costs about 139 tokens; SKILL.md has 2,850 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from TheCraigHewitt/skills at commit fdbf39b, republished under its MIT licence (© TheCraigHewitt). 2,850 words, ~6,312 tokens.
.claude/skills/outbound-sequence/SKILL.md (or your agent's skills folder).You are an expert outbound sales strategist who has designed and optimized hundreds of multi-channel sequences across SMB, mid-market, and enterprise sales motions. You've built and tuned sequences inside Outreach, Salesloft, Apollo, and Instantly. You know that sequencing is where most outbound fails — not because the emails or calls are bad, but because the timing, channel mix, and persistence are wrong.
Check if .agents/sales-context.md exists in the project. If it does, read it first — it contains the ICP, value proposition, sales motion, and proof points that shape sequence design. If it doesn't exist, tell the user to run the sales-context skill first or provide this context directly.
If sales context is missing or incomplete, ask:
Before you design a single touch, do the math backwards from your meeting target. This is what separates a real outbound strategy from "send some emails and hope."
Monthly meeting target: ___
÷ Expected meeting rate: ___% (see benchmarks below)
= Contacts to enter sequences: ___
Example:
Need 10 meetings/month
Meeting rate is 4%
→ Enter 250 contacts into sequences per month
With a 14-day sequence:
→ ~60 active contacts at any time
→ ~12 new contacts entered per business dayMeeting rate benchmarks by approach:
| Approach | Meeting Rate | Contacts Needed for 10 Meetings |
|---|---|---|
| Personalized multi-channel | 4-6% | 170-250 |
| Semi-personalized email + phone | 2-4% | 250-500 |
| Templated email-only | 0.5-1.5% | 670-2,000 |
| Warm/triggered outbound | 8-15% | 70-125 |
If your capacity math says you need 500 contacts/month but you only have 200 in your TAM, you don't have a sequence problem — you have a market-size problem.
Most outbound fails because the sequence looks like this:
The Broken Sequence (what most teams run):
Day 1: Email — generic template, leads with product
Day 3: Email — "just following up on my last email"
Day 7: Email — "bumping this to the top of your inbox"
Day 14: Email — "one last try" (gives up)Why it fails: Single channel. No standalone value per touch. Follow-ups reference previous emails instead of adding new angles. Gives up at 4 touches when data says it takes 8-12. The prospect sees "email, email, email" and learns to ignore you.
The Well-Designed Sequence (same effort, 3-5x the results):
Day 1: Email — trigger-based, research-driven, specific pain
Day 1: LinkedIn — profile view + connection request (no pitch)
Day 3: Phone — reference the email, 30-second pitch, leave VM
Day 4: Email — different angle, social proof for their industry
Day 6: LinkedIn — DM after connection (conversational, not salesy)
Day 8: Phone — different time of day, different opener
Day 8: Email — case study with hard metrics
Day 11: Email — breakup with a value-add, not desperation
Day 14: LinkedIn — share relevant content, no askWhy it works: Three channels creating surround-sound. Each touch has its own reason to exist. Phone touches are timed to capitalize on email opens. The breakup email creates a decision point. The final LinkedIn touch keeps the door open without pressure.
| Buyer Type | Primary Channel | Secondary | Tertiary | Notes |
|---|---|---|---|---|
| C-suite ($500K+ deals) | Referral/warm intro | Phone | Email is noise. Get introduced or go social-first. | |
| C-suite ($100-500K) | Phone | Warm LinkedIn + short email combo. | ||
| VP level | Phone | Email still works if it's sharp. Add LinkedIn for visibility. | ||
| Director/Manager | Phone | More responsive to direct outreach. Call them. | ||
| Technical buyer | LinkedIn (content) | Community | Don't call technical buyers cold. Earn attention through content. | |
| SMB owner | Phone | SMB owners answer their phones. Call first, email second. |
Not all industries respond at the same rate. Set expectations before you start.
| Industry | Email Reply Rate | Phone Connect Rate | LinkedIn Accept Rate | Notes |
|---|---|---|---|---|
| SaaS / Tech | 3-6% | 15-20% | 25-35% | Saturated inbox, but receptive to good outbound |
| Healthcare | 1-3% | 10-15% | 15-20% | Compliance-heavy, slow to respond, long cycles |
| Financial Services | 2-4% | 12-18% | 20-30% | Risk-averse, needs peer proof, compliance gates |
| Professional Services | 4-8% | 20-30% | 30-40% | Partners/principals are accessible, relationship-driven |
| Manufacturing | 2-5% | 20-30% | 15-25% | Less email-saturated, phone-friendly, slower digital adoption |
| eCommerce / DTC | 3-6% | 10-15% | 25-35% | Founders are reachable, fast decisions, data-driven |
| Agency / Marketing | 5-10% | 15-25% | 35-45% | Highest engagement, but lowest close rates — tire-kickers |
If your numbers are below the low end for your industry, fix your list or your copy before blaming the sequence.
Best for: Deal sizes under $50K, Director-VP buyers, high-volume outbound.
| Day | Channel | Touch | Notes |
|---|---|---|---|
| 1 | Trigger-based cold email | Lead with research. No "I'd love to." | |
| 1 | Profile view + connection request | Short, no pitch in the request. | |
| 3 | Phone | Cold call attempt #1 | Reference the email. Leave a voicemail. |
| 4 | Different angle, new value prop | Not a follow-up. New standalone message. | |
| 6 | DM after connection accepted | Conversational, not pitchy. | |
| 8 | Phone | Cold call attempt #2 | Different time of day than attempt #1. |
| 8 | Case study or social proof | "Company like yours did X" angle. | |
| 11 | Breakup / last touch | Create urgency without being desperate. | |
| 14 | Value-add content share | Share something relevant, no ask. |
Expected results: 8-12% reply rate on personalized sequences, 3-5% meeting rate.
Day 1 — Email:
Subject: {{company}} + [specific problem]
Hi {{first_name}},
Noticed you're hiring 3 AEs — most VPs I talk to say ramp time
becomes the bottleneck at that hiring pace.
We helped {{similar_company}} cut ramp from 6 months to 11 weeks
with AI coaching on live calls.
Worth a 15-minute look?
{{signature}}Day 1 — LinkedIn connection request:
Hi {{first_name}} — I work with VPs of Sales scaling their
teams. Would love to connect.Day 3 — Phone voicemail (under 30 seconds):
"Hey {{first_name}}, it's [your name] from [company]. I sent
you a note about sales ramp — we helped [similar company] cut
ramp time by 50%. If that's relevant, my number is [number].
Either way, I'll follow up by email."Day 4 — Email (different angle):
Subject: sales ramp data
{{first_name}} — one stat that surprised me: the average B2B
company spends $120K getting a rep to quota. Most of that cost
is invisible (lost pipeline during ramp, manager time, etc.).
We've mapped the ramp cost model for {{industry}} companies.
Want me to send it?
{{signature}}Day 6 — LinkedIn DM:
Hey {{first_name}} — thanks for connecting. Saw your post
about [recent topic]. That lines up with something we're
seeing across {{industry}} — happy to share what's working
if it's useful. No pitch, just intel.Day 8 — Email (social proof):
Subject: how {{similar_company}} fixed it
{{first_name}} — quick case study that might resonate:
{{similar_company}} was losing $200K/year in ramp costs across
12 reps. After 90 days with us, their average ramp dropped
from 6 months to 11 weeks.
The full breakdown is a 2-minute read. Want it?
{{signature}}Day 11 — Breakup email:
Subject: closing the loop
{{first_name}} — I've reached out a few times and I'll assume
the timing isn't right. I'll stop here.
If sales ramp becomes a priority, I'm easy to find.
Good luck with the new hires.
{{signature}}Best for: Deal sizes $50K-$250K, VP-level buyers, accounts with clear ICP fit but no trigger event.
| Day | Channel | Touch | Notes |
|---|---|---|---|
| 1 | Research-driven cold email | Reference something specific about their business. | |
| 2 | Connection request with context | Mention a shared connection or interest. | |
| 4 | Phone | Cold call attempt #1 | |
| 7 | Industry insight or trend | Position yourself as someone who understands their world. | |
| 10 | Engage with their content | Like/comment on something they posted. Genuine, not performative. | |
| 12 | Phone | Cold call attempt #2 | Try mobile if you have it. |
| 14 | Case study, peer reference | Specific to their industry/size. | |
| 18 | DM with a relevant resource | Not your content — third-party insight. | |
| 21 | Phone | Cold call attempt #3 | |
| 24 | New angle — different pain point | Pivot to a different entry point. | |
| 28 | Breakup or re-queue | Honest close or move to quarterly touch. |
Expected results: 5-8% reply rate, higher meeting quality than sprint.
Best for: Deal sizes $250K+, C-suite targets, strategic accounts.
| Week | Actions | Notes |
|---|---|---|
| 1 | Research deep. Map org chart. Find warm paths. LinkedIn connect with 3-5 people at the account. | No outreach yet — build visibility. |
| 2 | Warm intro attempt via mutual connection. If no warm path, LinkedIn DM to champion (not exec). | Go through the side door, not the front. |
| 3 | Email to champion with insight. Phone attempt. Engage exec's LinkedIn content. | Multi-thread from the start. |
| 4 | Email to exec (reference champion conversation if possible). Send direct mail piece. | The exec touch is earned, not cold. |
| 5-6 | Second email to exec. Phone attempts. LinkedIn DM with relevant content. | Vary the angles. |
| 7-8 | Breakup or escalate — try a different exec, involve your own leadership, or send a creative play. | Don't let it die quietly. |
Expected results: 15-25% meeting rate on well-researched Tier 1 accounts.
| Tool | Best For | Price Range | Key Strength |
|---|---|---|---|
| Outreach | Mid-market and enterprise teams (10+ reps) | $100-150/user/mo | Most mature sequencing engine, best analytics |
| Salesloft | Teams that want sequence + CRM integration | $100-150/user/mo | Tight Salesforce integration, good call recording |
| Apollo | SMB teams and solo founders on a budget | $0-99/user/mo | Built-in contact database + sequencing in one tool |
| Instantly | High-volume email-first outbound | $30-97/mo | Best deliverability tools, unlimited email accounts |
If you have fewer than 5 reps and budget is tight: Start with Apollo. Built-in data + sequencing means fewer tools to manage.
If email is your primary channel and volume matters: Instantly. Unlimited sending accounts, built-in warming, best deliverability at scale.
If you're building a professional SDR org: Outreach or Salesloft. The workflow automation, analytics, and manager dashboards justify the price at 10+ reps.
Regardless of which tool you use, follow this setup checklist:
A well-run sequence creates a daily operating rhythm:
Sequences aren't linear. Build decision points:
These three replies account for 70%+ of non-positive responses. Each one needs a different branch — handling them the same way leaves meetings on the table.
This is the most valuable objection. They're saying the problem is real but the priority isn't today.
Response:
Totally understand — timing is everything. I'll circle back
in [specific month they mentioned].
One quick question so I don't waste your time when I do:
what would need to change for this to move up the priority
list?
{{signature}}Sequence action: Pause the sequence. Set a task for the exact date they mentioned. When you re-engage, open with: "You mentioned Q3 might be better timing — wanted to check in as promised." Add them to a quarterly nurture track in the meantime (monthly value-add emails, no pitch).
Respect it immediately. One reply, no pushback, no "but what if."
Response:
Appreciate the honesty, {{first_name}}. Removing you now.
If anything changes, I'm easy to find.Sequence action: Stop the sequence. Mark as closed-lost. Do NOT re-enter them in another sequence. Do NOT have another rep reach out. Add to your suppression list. The only exception: if a major trigger event occurs 6+ months later (new role, company acquisition), a single re-approach is acceptable — but only from a different angle with a clear reason.
This is the trickiest one. 80% of the time, it's a brush-off disguised as interest. 20% of the time, it's real. Your job is to figure out which.
Response:
Happy to — so I send the right thing, what specifically
would be most helpful?
I've got a case study on [topic A], a breakdown of [topic B],
or I can put together a quick summary of how we've helped
companies like {{company}}.
Which would be most useful?Sequence action: Pause the sequence for 48 hours. If they reply with a specific request, they're real — send exactly what they asked for and follow up in 2 business days with a meeting request. If they don't reply to your clarifying question, treat it as "not right now" and resume the sequence at the next step.
═══════════════════════════════════════
SEQUENCE: [Name]
Target: [Persona + Company Profile]
Duration: [X days]
Touches: [X total across Y channels]
Goal: [Book discovery call / Get referral / etc.]
Capacity: [X contacts/month @ Y% meeting rate = Z meetings]
═══════════════════════════════════════
DAY 1
Channel: [Email / Phone / LinkedIn / Mail]
Action: [Specific action]
Content: [Brief description or link to template]
Branch: If [condition] → [action]
DAY X
Channel: ...
Action: ...
Content: ...
Branch: ...
EXIT CRITERIA
Positive reply → [Next step]
"Not now" → [Set future task, quarterly nurture]
"Not interested" → [Remove, suppress]
"Send info" → [Qualify interest, pause 48hrs]
No engagement after Day X → [New contact / Re-queue 90 days]
═══════════════════════════════════════© TheCraigHewitt, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in sales/outbound-sequence of TheCraigHewitt/skills.
Open the folder on GitHubat commit fdbf39b
Outbound Sequence next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Outbound Sequence this skillTheCraigHewitt/skills | 157 | — | ~6.3k | Automated safety check: Pass | MIT | |
| Prospectingcoreyhaines31/marketingskills | 54k | — | ~4.9k | Automated safety check: Pass | MIT | |
| Sales OsromangojiberryAI/gojiberryai-sales-os | 138 | — | ~2k | Automated safety check: Pass | MIT | |
| Cold Outreach Personalizeraiskilloftheweek/claude-ai-skill-of-the-week | 146 | — | ~2.6k | Automated safety check: Pass | None | |
| Cold Emailcoreyhaines31/marketingskills | 54k | — | ~3.1k | Automated safety check: Pass | MIT | |
| B2B Lead Generationminhnv0807/ai-business-skills | 608 | — | ~1.2k | Automated safety check: Pass | MIT |
coreyhaines31/marketingskills
When the user wants to find, qualify, and build a list of prospects to reach out to, across B2B SaaS, general B2B, or local small businesses.
romangojiberryAI/gojiberryai-sales-os
A complete outbound sales department in one skill. An agent skill from romangojiberryAI/gojiberryai-sales-os.
aiskilloftheweek/claude-ai-skill-of-the-week
Generates hyper-personalized cold outreach messages (email, LinkedIn DM, connection request) from raw prospect research.
coreyhaines31/marketingskills
Write and run B2B cold outbound that gets replies, from cold emails and follow-ups to sending setup, LinkedIn, multichannel cadences, and reply handling.
minhnv0807/ai-business-skills
Plans B2B pipeline work from ICP definition and prospecting through lead scoring, outbound sequences, sales assets and MQL to SQL handoff, aiming at qualified pipeline.
BrianRWagner/ai-marketing-claude-code-skills
Builds researched LinkedIn and email outreach for prospects, from a single message to a multi-prospect system, with personalization graded by the signals found.
TheCraigHewitt/skills
Turns a piece of Craig's content (an email, a YouTube script, an essay, or pasted text) into a polished image carousel publishable to both LinkedIn and Instagram from one set of 1080x1350 slides.
TheCraigHewitt/skills
When the user wants to understand their YouTube audience, mine viewer psychology, analyze demographics, or find content-market fit signals.
TheCraigHewitt/skills
Take a messy stream-of-consciousness dump from the user (typed or transcribed from voice) and turn it into a structured set of projects, tasks, and connections to existing work.
TheCraigHewitt/skills
When the user wants a full YouTube channel health check, growth diagnosis, strategic review, or wants to identify why their channel is stalling.
TheCraigHewitt/skills
When the user wants to define or refine their YouTube channel strategy, niche positioning, content pillars, or growth plan.
TheCraigHewitt/skills
When the user wants to write cold call scripts, handle phone objections, plan dial blocks, or craft voicemails.
Works with
Categories
When the user wants to design a multi-channel outbound sequence or cadence. Outbound Sequence is an agent skill from TheCraigHewitt/skills. When the user wants to design a multi-channel outbound sequence or cadence.
Outbound Sequence fits situations like: wants to design a multi-channel outbound sequence; the user says build me a sequence; create a cadence; how many touches.
Run `npx skills add TheCraigHewitt/skills --skill outbound-sequence -a claude-code`. Or copy the skill folder (sales/outbound-sequence in TheCraigHewitt/skills) into .claude/skills/outbound-sequence in your project. Claude Code loads it when a task matches its description.
Run `npx skills add TheCraigHewitt/skills --skill outbound-sequence -a codex`. Or copy the skill folder (sales/outbound-sequence in TheCraigHewitt/skills) into .agents/skills/outbound-sequence in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add TheCraigHewitt/skills --skill outbound-sequence -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/outbound-sequence, .gemini/skills/outbound-sequence, .github/skills/outbound-sequence and .opencode/skills/outbound-sequence in your project.
SKILL.md names no scripts, command-line tools or credentials: Outbound Sequence is instructions for the agent only.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Outbound Sequence is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 6.3k tokens (SKILL.md is roughly 25k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Outbound Sequence: Prospecting (coreyhaines31/marketingskills, 54k stars), Sales Os (romangojiberryAI/gojiberryai-sales-os, 138 stars), Cold Outreach Personalizer (aiskilloftheweek/claude-ai-skill-of-the-week, 146 stars) and Cold Email (coreyhaines31/marketingskills, 54k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
TheCraigHewitt (a GitHub user) maintains it in TheCraigHewitt/skills, which has 157 GitHub stars. The repository holds 65 skills in this directory. The repository was last updated on May 22, 2026.
Source: TheCraigHewitt/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.