leads
Skill0 starsChanged 8 months agoMITView on GitHub
Inbound lead triage and follow-up. Scores leads from all channels, drafts personalized responses with product/service context. Run 2-3x daily. Octopus colors: Yellow (scoring) + Green (outreach).
5 other projects use a version of this.
Adopted by
Most recently taken up by
- advisorppc-org/advisorseo-claude-plugintheir own version, first seen Nov 1, 2026
- HalberdLLC/leadmerlin-skilltheir own version, first seen Oct 20, 2026
- greglas75/zuvotheir own version, first seen Oct 16, 2026
- donatassimkus/claude-ai-skillstheir own version, first seen Jul 23, 2026
- velasco810/claude-code-linkedintheir own version, first seen Apr 2, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- greglas75/zuvo★ 7same name
- donatassimkus/claude-ai-skills★ 1same name
- velasco810/claude-code-linkedin★ 1same name
- advisorppc-org/advisorseo-claude-plugin★ 0same name
- HalberdLLC/leadmerlin-skill★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 0 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Read .chairman/config.json for business context
- Very specific: line 15
Read departments/commercial/knowledge/ for products, pricing, and sales playbooks
- Very specific: line 50
Never send without Chairman approval until trust level is "mature"
“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/leads: Lead Triage and Follow-up
Octopus Colors: Yellow (Researcher) + Green (Marketer)
Process
- Read
.chairman/config.jsonfor business context - Read
departments/commercial/knowledge/for products, pricing, and sales playbooks - Gather leads: check $ARGUMENTS for specific leads, or ask the Chairman what came in
- For each lead, score (Yellow):
- Intent signals (browsing vs. buying)
- Budget indicators
- Fit with offerings
- Source quality and urgency
- Score 0-100
- Draft follow-up (Green):
- Personalize to the lead's specific interest
- Reference relevant product/service
- Include one proof point or case study reference
- Match tone to channel (formal for email, conversational for WhatsApp)
- Present to Chairman for review
Output Format
For each lead:
## Lead: [Name/Company]
Score: [0-100] | Channel: [source] | Intent: [browsing/considering/ready]
### Context
[What they showed interest in, any background]
### Drafted Follow-up
[The message, ready to send]
### Approval: [ ] Send as-is [ ] Edit first [ ] SkipRules
- Hot leads (score > 80): flag for immediate Chairman review
- Warm leads (40-80): draft follow-up, queue for batch review
- Cold leads (< 40): log, add to nurture list, no immediate action
- Never send without Chairman approval until trust level is "mature"
- Log all leads to
departments/commercial/knowledge/pipeline.md
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

