bundles/sales/skills/outbound-optimizer/SKILL.md
Transforms cold outreach from spam into revenue using Hormozi value-first principles. Triggers when a user needs to improve cold emails or DMs, increase response rates, diagnose low-converting outreach sequences, or build a prospecting strategy.
npx skillsauth add shipshitdev/library outbound-optimizerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Executes an outreach transformation using Alex Hormozi's outbound principles — diagnosing current messaging and producing high-converting templates that lead with value, prove personalization, and make zero-commitment offers.
Hormozi's Core Principle: "Outbound is the fastest way to revenue. Most people just suck at it. Lead with value, not pitch."
Key Principles:
Ask the user:
Who exactly are you reaching out to?
- What's their job title/role?
- What company size/type?
- What industry or vertical?
- What pain are they experiencing RIGHT NOW?
- Why should THEY specifically care about what you offer?
- What would make them say "this person actually gets my situation"?
ICP Framework:
| Element | Question | Example | |---------|----------|---------| | Title | Who decides? | Marketing Directors | | Company | What type? | B2B SaaS, $1-10M ARR | | Pain | What hurts? | Content isn't converting to leads | | Trigger | Why NOW? | Just raised funding, hiring marketers | | Proof | Why YOU? | We helped [similar company] get [result] |
Ask the user:
Share your current outreach message(s):
- What's your current cold email or DM?
- What's your subject line?
- What's your response rate? (Be honest)
- What responses do you typically get?
- How many do you send per day/week?
Common Problems to Diagnose:
| Issue | Symptom | Fix | |-------|---------|-----| | Too long | Wall of text | Under 100 words | | No hook | Boring first line | Lead with insight | | No research | Generic message | Personalize first line | | All about YOU | "I/We/Our" focus | Talk about THEM | | Pushy CTA | "Book a call" immediately | Zero-commitment offer | | No value | Just asking for time | Give something first |
Formula:
[Personalized opener showing research]
[Observation/insight about their situation]
[Value you can offer for free]
[Zero-commitment CTA]
First Sentence Test:
Component 1: The Hook (First Line)
Make it impossible to ignore. Prove you know them.
Good Examples:
Bad Examples:
Component 2: The Observation
Show you understand their world.
Good Examples:
Component 3: The Value Offer
Give before you ask.
Zero-commitment offers:
Component 4: The CTA
Make it natural and low-friction.
Good CTAs:
Bad CTAs:
Sequence Framework:
| Email | Timing | Purpose | |-------|--------|---------| | #1 | Day 0 | Initial value offer | | #2 | Day 3 | Bump with additional value | | #3 | Day 7 | Different angle/insight | | #4 | Day 14 | Social proof or case study | | #5 | Day 21 | Break-up email |
Follow-Up Templates:
Email 2 (Value Bump):
"Quick follow-up — [additional insight or value]. [Restate offer]."
Email 3 (Different Angle):
"[New observation about their business]. Thought this might be relevant."
Email 4 (Social Proof):
"Just helped [similar company] with [result]. Thought of you."
Email 5 (Break-Up):
"Closing the loop on this. If [problem] isn't a priority right now, no worries. Door's open when it is."
When They Respond Positively:
When They Say "Not Now":
"Totally understand. Mind if I check back in [timeframe]? Things change."
When They Ask "What's This About?":
"In short: [1-sentence value prop]. [Offer the value you promised]. Happy to share more if helpful."
When They're Skeptical:
"[Acknowledge concern]. Totally fair. [Proof point]. Happy to share [example/case study] if useful."
# Outbound Optimization: [Business/Offer Name]
## ICP Definition
**Target:**
- **Title:** [Job title/role]
- **Company:** [Size, type, industry]
- **Pain:** [Core problem they have]
- **Trigger:** [Why they'd care NOW]
- **Proof Point:** [Why you can help]
## Current Message Audit
**Your Current Message:**
> [Their current outreach]
**Issues Identified:**
1. [Problem 1] — [Why it hurts performance]
2. [Problem 2] — [Why it hurts performance]
3. [Problem 3] — [Why it hurts performance]
**Response Rate:** X% (Target: 5-10% for cold email)
## Optimized Outreach
### Email 1: Initial Outreach
**Subject:** [Subject line]
**Body:**
> [Full rewritten message]
**Why It Works:**
- Hook: [Why the first line works]
- Value: [What you're offering]
- CTA: [Why the CTA is low-friction]
### Email 2: Follow-Up (Day 3)
**Subject:** [Subject line]
**Body:**
> [Follow-up message]
### Email 3: Different Angle (Day 7)
**Subject:** [Subject line]
**Body:**
> [Different angle message]
### Email 4: Social Proof (Day 14)
**Subject:** [Subject line]
**Body:**
> [Social proof message]
### Email 5: Break-Up (Day 21)
**Subject:** [Subject line]
**Body:**
> [Break-up message]
## Personalization Framework
### Research Checklist
For each prospect, find:
- [ ] Recent post, article, or interview
- [ ] Company news or announcement
- [ ] Hiring activity or new roles
- [ ] Technology they use
- [ ] Mutual connections
### Personalization Templates
**Pattern 1: Content-Based**
> "Your [post/article] on [topic] resonated — especially [specific point]."
**Pattern 2: Hiring Signal**
> "Noticed you're hiring [role] — usually means [pain you solve]."
**Pattern 3: Company News**
> "Saw the news about [event]. [Insight about what it means]."
**Pattern 4: Mutual Connection**
> "[Name] mentioned you're working on [project]. Made me think of [value]."
## Response Scripts
### Positive Response
> "[Thanks]. Here's [value you promised]. Quick question: [qualifying question]? If [condition], [specific next step]."
### "Not Now" Response
> "No problem at all. Would it make sense to reconnect in [timeframe]? Happy to check back then."
### "What's This?" Response
> "Good question. [1-sentence value prop]. [Reoffer the value]. Worth a look?"
### Skeptical Response
> "Totally fair to ask. [Proof point — specific result for similar company]. Happy to share the case study if helpful."
## Metrics to Track
| Metric | Current | Target |
|--------|---------|--------|
| Emails Sent/Day | X | X |
| Open Rate | X% | 40%+ |
| Response Rate | X% | 5-10% |
| Positive Response Rate | X% | 3-5% |
| Meetings Booked/Week | X | X |
| Meeting → Customer Rate | X% | X% |
## Implementation Checklist
### This Week
- [ ] Finalize ICP definition
- [ ] Set up email/sending tool
- [ ] Create personalization research process
- [ ] Write and load email sequence
- [ ] Send first batch of 20-50 emails
### Ongoing
- [ ] Send X outreach per day
- [ ] A/B test subject lines
- [ ] Track response patterns
- [ ] Iterate on messaging weekly
Quality + Volume = Results
| Stage | Volume | Focus | |-------|--------|-------| | Testing (Week 1-2) | 20-50/day | Find what works | | Scaling (Week 3-4) | 50-100/day | Systematize | | Cruising (Month 2+) | 100+/day | Maintain and iterate |
Rule: Never sacrifice personalization for volume. Better to send 50 great emails than 500 spam.
| Skill | How It Works Together |
|-------|----------------------|
| leads-researcher | Find and research prospects |
| offer-architect | Make the offer being pitched irresistible |
| copywriter | Polish the messaging |
| lead-channel-optimizer | Compare outbound to other channels |
| execution-accelerator | Stop overthinking, start sending |
Example:
That's 4-8 customers/month from outbound alone.
lead-channel-optimizeroffer-architectexecution-acceleratorpricing-strategistdevelopment
Coordinates a weekly engineering review of board accuracy, recent code changes, operational health, and scoped cleanup. Use for a recurring repository health review or a review of the last several days.
testing
Audits project board configuration and prepares explicitly requested setup, copy, or normalization changes while preserving the existing workflow and provider boundaries. Use when inspecting a board's fields, columns, scope, or configuration.
testing
Reconciles a project board with current work and delivery evidence, reports incomplete coverage and metadata gaps, and applies only approved provider-supported field changes. Use when auditing board drift, reviewing blocked work, or assessing upcoming delivery.
development
Walk through how a subsystem works. Use for "how does X work", code walkthroughs before changing something, and placement or ownership questions. Explains architecture, runtime flow, and onboarding mental models. Can critique architecture. Use why for motivation.