agentleFS
kronus-techkronus-tech/kronus/.claude/skills/lead-qualify/SKILL.md

lead-qualify

Skill4 starsChanged 7 months agoMITView on GitHub

Score and qualify an inbound lead based on budget, timeline, technical fit, and engagement signals. Auto-invoked when user says "qualify this lead", "score this lead", "is this worth pursuing".

Files
SKILL.md

Analyze the following lead and score it right now:

Lead info: $ARGUMENTS

Score on these 5 criteria (1-10 each):

CriteriaWeightScoreReasoning
Technical fit (AI/RAG/full-stack match)30%?
Budget (realistic for scope)25%?
Client quality (communication, clarity, hire history)20%?
Timeline (feasible delivery)15%?
Growth potential (repeat work, referrals, portfolio)10%?

Overall: weighted average

Verdict:

  • Hot (8+): Apply immediately
  • Warm (6-7.9): Worth pursuing
  • Cold (below 6): Skip or low-effort

Then provide:

  • Recommended response approach
  • Key questions to ask the client
  • Red flags (if any)
  • Estimated effort to complete the work

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.