Localized reading guide
outreach-composerPurpose, usage and source
Writes prospect outreach and follow-up sequences that sound like the owner wrote them, not like an AI did. Learns a voice profile from the owner's own sent mail, grounds every message in something specific about that prospect, builds the follow-up sequence behind it, queues every send for approval, and logs each touch to the CRM. Runs draft-only when no mail connector is available, so the copy can be pasted anywhere. Use this whenever the owner needs to reach out to prospects or customers — including phrasings like "write this cold email," "draft a follow-up," "reach out to these leads," "what do I say to them," "I need a sequence for this list," "nudge the people who didn't reply," or "write it but don't make it sound like a robot." Reach for it whenever outreach copy is the deliverable, even for a single message.
Source retrieved:
- Source repository
- anthropics/knowledge-work-plugins
- SKILL.md
small-business/skills/outreach-composer/SKILL.md- Repository stars
- 34,049
- Repository updated
- 2026-10-30
- Categories
- Business
- Last collected
License: Apache-2.0
Workflow excerpts are reading aids, not executable instructions from Codez. No third-party Skill was run to produce this page.
The purpose and workflow passages below are upstream material, organized and translated for reading. They are distinct from the separately labeled Codez editorial analysis.
What this Skill does
Writes prospect outreach and follow-up sequences that sound like the owner wrote them, not like an AI did. Learns a voice profile from the owner's own sent mail, grounds every message in something specific about that prospect, builds the follow-up sequence behind it, queues every send for approval, and logs each touch to the CRM. Runs draft-only when no mail connector is available, so the copy can be pasted anywhere. Use this whenever the owner needs to reach out to prospects or customers — including phrasings like "write this cold email," "draft a follow-up," "reach out to these leads," "what do I say to them," "I need a sequence for this list," "nudge the people who didn't reply," or "write it but don't make it sound like a robot." Reach for it whenever outreach copy is the deliverable, even for a single message.
How the upstream workflow works
Step 1 — Learn the voice before writing anything
Read the shared voice profile first. If a profile already exists there, use it and skip to Step 2 — rebuilding it every time wastes the owner's patience and produces drift. If there is no profile, build one from evidence: Gmail or Microsoft 365 — pull 15 to 30 of the owner's own sent messages to customers and prospects. This is the best source by a wide margin. Confirm the mailbox is the owner's first (../../shared/tenant-scope.md); another tenant's sent mail would teach the wrong voice. HubSpot — logged emails and notes
Step 2 — Ground each message in something real
A personalized email is not one with the company name merged into a template. It is one that could only have been sent to that person. For each prospect, find the specific hook. In order of strength: The buying signal from lead-finder — a permit filed, a location opened, a role posted A shared connection or customer
Step 3 — Write the sequence
Read reference/sequence_patterns.md for structure by scenario. Defaults: Cold outreach — 4 messages over 3 weeks Warm or referral — 3 messages over 2 weeks Post-meeting follow-up — 2 messages over 10 days
Requirements and setup
No short requirements passage was selected from this file. This does not mean the Skill has no dependencies. Check the repository setup instructions and referenced files.
Limits and quality checks
No separate limits passage was selected from this file. This does not mean the Skill is safe for every input or environment. Review the complete source and validate your own result.
Start with a safe trial
- Check the supported host and the repository installation instructions. Keep the Skill directory and its referenced scripts, assets and documentation together; SKILL.md alone may omit dependencies.
- Give the agent your real input, desired output and acceptance criteria. Invocation syntax and available tools depend on the host; this site does not assume a universal install command.
- Try the source workflow in a disposable project or on a copy. Review operations that change files, remote services or billable resources before allowing them.
- Validate the output against the source quality checks and your own requirements. A successful trigger or a high repository Star count does not establish a correct result.
Read further in the source
- Outreach Composer
- Step 1 — Learn the voice before writing anything
- Step 2 — Ground each message in something real
- Step 3 — Write the sequence
- Step 4 — Self-check against the slop test
- Step 5 — Present for approval
- Step 6 — Queue sends, with approval, one gate at a time
- Step 7 — Log it
- What not to do
- After the send
- Reference files
- Using a tool that isn't listed
Related Skills
Translation and scope
This reading guide selects passages from the pinned upstream SKILL.md. Translation is assisted. It is not a complete manual or a claim of tested compatibility. Read the original and its referenced files before use.
This introduction refers to the pinned version below; current repository activity and collection time are shown separately.
- Pinned source
- Read the original ↗
- Source retrieved
- Source commit
2574e29377c7173d0cecffef29a6ecbd7f8ccb5d- Source SHA-256
6d66654d83db4c955ae82e8618b51cfca617f10dc1822eb4e05a1ad4b2ea6ac9