agentleFS
victordelrosalvictordelrosal/chairman/.claude/skills/leads/SKILL.md

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

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
  1. Very specific:

    Read .chairman/config.json for business context

    line 14
  2. Very specific:

    Read departments/commercial/knowledge/ for products, pricing, and sales playbooks

    line 15
  3. Very specific:

    Never send without Chairman approval until trust level is "mature"

    line 50

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

/leads: Lead Triage and Follow-up

Octopus Colors: Yellow (Researcher) + Green (Marketer)

Process

  1. Read .chairman/config.json for business context
  2. Read departments/commercial/knowledge/ for products, pricing, and sales playbooks
  3. Gather leads: check $ARGUMENTS for specific leads, or ask the Chairman what came in
  4. For each lead, score (Yellow):
    • Intent signals (browsing vs. buying)
    • Budget indicators
    • Fit with offerings
    • Source quality and urgency
    • Score 0-100
  5. 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)
  6. 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  [ ] Skip

Rules

  • 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

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.