Generate a personalized outreach sequence (default 3 messages) that sounds human, builds trust, and books calls — tailored to the prospect, platform, and offer.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionoutreach-specialistExecute the skills CLI command in your project's root directory to begin installation:
Fetches outreach-specialist from ognjengt/founder-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate outreach-specialist. Access via /outreach-specialist in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
110
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
110
stars
Generate a personalized outreach sequence (default 3 messages) that sounds human, builds trust, and books calls — tailored to the prospect, platform, and offer.
Check $ARGUMENTS first to determine execution mode:
Respond with: "outreach-specialist loaded, tell me who you're reaching out to and what you're offering"
Then wait for the user to provide their requirements in the next message.
Proceed immediately to Task Execution (skip the "loaded" message).
When user requirements are available (either from initial $ARGUMENTS or follow-up message):
BLOCKING REQUIREMENT — DO NOT SKIP THIS STEP
Before doing ANYTHING else, you MUST use the Read tool to read ALL reference files. This is non-negotiable:
Read: ./references/outreach-templates.md
Read: ./references/sequence-strategy.md
What you will find:
DO NOT PROCEED to Step 2 until you have read all files and have their content in context.
Check if FOUNDER_CONTEXT.md exists in the project root.
From the user's requirements, extract:
If you are NOT 100% certain you have everything needed to write a high-converting message, ask up to 5 questions using AskUserQuestion. Only ask what's genuinely missing.
Question Bank (priority order):
| # | Question | Why it matters | Skip if... |
|---|---|---|---|
| 1 | Are you reaching out on LinkedIn, email, or another platform? | Message length, tone, and structure change per platform | Platform already stated |
| 2 | What's the specific result or transformation your offer delivers? | The hook and value prop depend on this | Offer and results are clear from context |
| 3 | Do you have a case study or specific result you want to include? | Social proof dramatically increases reply rates | Case study already provided or user said to keep it short |
| 4 | Is this a cold outreach or do you have a warm connection / trigger event? | Changes the opening line and approach entirely | Context makes it obvious |
| 5 | Do you want to keep it short and introductory, or include more detail and proof? | Determines message length and template selection | User already specified format preference |
Ask up to 4 questions per batch. Stop as soon as you have enough to write a confident sequence.
Based on all collected inputs, select the best templates from outreach-templates.md:
Template Selection Logic:
| Situation | Best template match |
|---|---|
| Cold outreach, no prior relationship | Taking on New Projects, Value-First, or Permission-Based |
| Have a strong case study to share | Case Study template |
| Found something specific about the prospect | Firstline template |
| Warm intro or mutual connection exists | Mutual Connection template |
| Want to stand out with multimedia | Loom/Video Teaser template |
| Referral-based approach | Taking on New Projects (with referral angle) |
| Final follow-up in sequence | Breakup template |
Sequence Structure (default 3 messages):
If the user requests more or fewer messages, adjust accordingly.
For each message in the sequence:
Hard constraints. No interpretation.
Present the full sequence with platform, timing, and ready-to-send messages:
## Outreach Sequence
**Target:** [Who the outreach is for]
**Platform:** [LinkedIn / Email / X DM / etc.]
**Goal:** [Book a call / Get a reply / etc.]
**Sequence length:** [X messages]
---
### Message 1 — Initial Outreach
**Send:** Day 1
**Subject:** [Only for email — omit for DMs]
[Full message text, ready to copy and send]
---
### Message 2 — Follow-Up
**Send:** Day 3-4
**Subject:** [Only for email]
[Full message text, ready to copy and send]
---
### Message 3 — Final Touch
**Send:** Day 7-10
**Subject:** [Only for email]
[Full message text, ready to copy and send]
Example:
## Outreach Sequence
**Target:** B2B SaaS founders doing $1M-$5M ARR
**Platform:** LinkedIn DM
**Goal:** Book a discovery call
---
### Message 1 — Initial Outreach
**Send:** Day 1
Hey John,
Saw you're scaling the sales team at Acme. Nice.
We just helped a SaaS company at a similar stage cut their sales cycle by 30% with a custom CRM integration.
Worth a quick 10-min chat to see if it fits?
---
### Message 2 — Follow-Up
**Send:** Day 3
Hey John,
Not trying to be pushy. Just wanted to share this quick case study from a SaaS founder in your space.
[link to case study]
Thought it might be useful whether we chat or not.
---
### Message 3 — Final Touch
**Send:** Day 8
Hey John,
Tried reaching out a couple of times, so I'll keep this short.
If cutting your sales cycle isn't a priority right now, totally get it.
But if it is, happy to chat for 10 min this week. Either way, good luck scaling the team.
These files MUST be read using the Read tool before generating any messages (see Step 1):
| File | Purpose |
|---|---|
./references/outreach-templates.md |
8 proven outreach message templates with examples, psychology, and when-to-use logic |
./references/sequence-strategy.md |
Follow-up sequence structures, timing, platform rules, and proven patterns |
Why both matter: Templates give you the structural DNA of messages that actually get replies. Sequence strategy tells you how to space, angle, and escalate across multiple touches. Templates alone = a good first message. Templates + sequence strategy = a full system that books calls.
Before finalizing output, verify ALL of the following:
./references/outreach-templates.md before writing messages./references/sequence-strategy.md before writing messagesIf ANY check fails, revise before presenting.
Use these unless the user overrides:
Document any assumptions made in the output.
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
ailabs-393/ai-labs-claude-skills
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
Solid pick for teams standardizing on skills: outreach-specialist is focused, and the summary matches what you get after install.
We added outreach-specialist from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Registry listing for outreach-specialist matched our evaluation — installs cleanly and behaves as described in the markdown.
I recommend outreach-specialist for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Useful defaults in outreach-specialist — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
I recommend outreach-specialist for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Keeps context tight: outreach-specialist is the kind of skill you can hand to a new teammate without a long onboarding doc.
Registry listing for outreach-specialist matched our evaluation — installs cleanly and behaves as described in the markdown.
outreach-specialist fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Solid pick for teams standardizing on skills: outreach-specialist is focused, and the summary matches what you get after install.
showing 1-10 of 48