Localized reading guide
speed-to-leadPurpose, usage and source
Makes sure no inbound lead goes unanswered. Watches web forms, the shared inbox, and the CRM for new inquiries, qualifies each one against the owner's criteria, drafts a reply in the owner's voice with real meeting times for the owner to approve and send, routes anything hot to a human right away, and logs the whole thing to the CRM. Never sends on its own. Built to run on a schedule so overnight inquiries are drafted and sorted by morning, and works from forwarded or pasted inquiries when no connector is available. Use this whenever the owner is worried about inbound leads or response time — including phrasings like "leads are going cold," "did anyone answer that inquiry," "I keep missing form submissions," "nothing falls through the cracks," "handle my inbound," "respond to this lead," or "we lose people because nobody gets back fast enough." Reach for it for a single unanswered inquiry as readily as for a standing setup.
Source retrieved:
- Source repository
- anthropics/knowledge-work-plugins
- SKILL.md
small-business/skills/speed-to-lead/SKILL.md- Repository stars
- 34,049
- Repository updated
- 2026-10-30
- Categories
- research
- 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
Makes sure no inbound lead goes unanswered. Watches web forms, the shared inbox, and the CRM for new inquiries, qualifies each one against the owner's criteria, drafts a reply in the owner's voice with real meeting times for the owner to approve and send, routes anything hot to a human right away, and logs the whole thing to the CRM. Never sends on its own. Built to run on a schedule so overnight inquiries are drafted and sorted by morning, and works from forwarded or pasted inquiries when no connector is available. Use this whenever the owner is worried about inbound leads or response time — including phrasings like "leads are going cold," "did anyone answer that inquiry," "I keep missing form submissions," "nothing falls through the cracks," "handle my inbound," "respond to this lead," or "we lose people because nobody gets back fast enough." Reach for it for a single unanswered inquiry as readily as for a standing setup.
How the upstream workflow works
Step 1 — Find what came in
Check every inbound channel in one parallel pass: Gmail or Microsoft 365 — the shared or sales inbox, filtered to inquiries, confirmed as the owner's before the first read (../../shared/tenant-scope.md) HubSpot — new contacts and form submissions since the last run Website form notifications — usually arriving as email
Step 2 — Qualify against the owner's actual criteria
Read reference/qualification.md. If criteria exist there, use them. If not, derive a starting set from the owner's closed-won history and confirm in one pass, rather than interviewing them from scratch. Sort each inquiry into one of four buckets: Hot — fits the profile and shows urgency. Route to a human now. Qualified — fits, no particular urgency. Answer and book time.
Step 3 — Draft the reply
Read the shared voice profile — it lives at shared/voice-profile.md, one file for the whole plugin, so every skill writing in the owner's name sounds the same. If it has no profile yet, follow its "When there is no sample" instruction — ask for three emails the owner was happy with; if they decline, write plain and neutral and say the reply is un-voiced. Never invent a personality. The reply follows the pattern in reference/response_patterns.md. Four things, in this order: Answer their actual question. Most inquiries ask something specific. Answering it is what separates a reply from an autoresponder. Confirm you can help, or say honestly that you can't.
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
- Speed to Lead
- Step 1 — Find what came in
- What RingEx Chat is for here
- Step 2 — Qualify against the owner's actual criteria
- Step 3 — Draft the reply
- Step 4 — Pull real meeting times
- Step 5 — Route the hot ones to a human
- Step 6 — Send only what the owner approved
- Step 7 — Log everything
- Step 8 — Report what happened
- Scheduled chain mode
- What not to do
- After the run
- 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
c30ccc85bf54e78bc66e204ef72d6f4954250a3516795c32a8a83e9572a5b1ac