agentleFS
nawazxznawazxz/20-claude-skills-for-business/lead-qualifier/SKILL.md

lead-qualifier

Skill0 starsChanged 3 months agoMITView on GitHub

Score and triage an inbound lead so a team knows who to call first. Use when someone pastes a lead's details, a contact form submission, or an inquiry email and asks whether it's worth pursuing or how to prioritize it.

2 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

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If the message is too thin to judge, ask for the missing pieces before scoring.

    line 14
  2. Distinctive:

    Never invent budget or intent that isn't in the message.

    line 34

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “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

Lead Qualifier

Turn a raw lead into a clear verdict: how good it is, why, and what to do next.

Inputs needed

  • The lead's details: name, company, message, and any of budget, timeline, role, source.
  • (Optional) The ideal customer profile. If none is given, infer a sensible one and say so.

If the message is too thin to judge, ask for the missing pieces before scoring.

Steps

  1. Pull out the signals: budget, authority (is this person a decision maker), need, timeline (BANT), plus fit to the ideal customer.
  2. Score each of the four BANT factors from 0-3 and total to a score out of 12.
  3. Map the score to a tier: Hot (9-12), Warm (5-8), Cold (0-4).
  4. Flag any risks or missing info that would change the score.
  5. Recommend the next action and a one-line opener the rep can use.

Output format

Tier: Hot / Warm / Cold  (score/12)
Why: 2-3 bullets on the strongest signals
Missing: what we still need to know
Next step: the single best action
Opener: one sentence the rep can send now

Voice & rules

  • Be honest. A weak lead scored Cold saves the team time.
  • Never invent budget or intent that isn't in the message.

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.