lead-scorer
Skill3 starsChanged 6 months agoMITView on GitHub
Score a list of leads 0 to 100 against your own ideal-client rubric and rank them into hot, warm, and cold tiers. Takes a CSV or markdown list of leads, scores each with a reason and a suggested next action, and outputs a ranked file. Honest about missing data: leads it cannot judge get flagged for research, not guessed. Use when the user says "score these leads", "rank this lead list", "prioritise my prospects", or "which of these should I contact first".
2 other projects use a version of this.
Adopted by
Most recently taken up by
- koinod/skillstheir own version, first seen May 22, 2026
- koinod/koino-skillstheir own version, first seen May 22, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- koinod/koino-skills★ 7same name
- koinod/skills★ 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.
In this repository47 other files it gives its agents.
- agents-md-writerSkill
- ai-image-run-pacingSkill
- automation-state-reconcilerSkill
- backup-readiness-auditorSkill
- brand-voice-linterSkill
- case-study-writerSkill
- client-delivery-auditorSkill
- client-intake-builderSkill
- client-workspace-scaffolderSkill
- code-deduplicatorSkill
- cold-outreach-writerSkill
- demo-animationSkill
- demo-animation-v2Skill
- discovery-briefSkill
- em-dash-removerSkill
- etsy-listing-optimizerSkill
- follow-up-radarSkill
- github-profile-proof-updaterSkill
- github-safe-publisherSkill
- idea-inboxSkill
- implement-client-feedbackSkill
- llms-txt-generatorSkill
- local-app-public-demoSkill
- media-spec-checkerSkill
- obsidian-daily-noteSkill
- ops-status-reportSkill
- outreach-pipeline-designerSkill
- php-form-mailerSkill
- proposal-writerSkill
- release-announcement-writerSkill
- remove-ai-image-metadataSkill
- research-brief-curatorSkill
- research-to-articleSkill
- screen-recorderSkill
- session-handoffSkill
- skill-builderSkill
- skill-reviewerSkill
- social-campaign-proof-trackerSkill
- skill-nameSkill
- thumbnail-legibility-checkSkill
- thumbnail-set-designerSkill
- vault-janitorSkill
- verify-public-claimsSkill
- web-scraperSkill
- website-change-verifierSkill
- windows-reinstall-plannerSkill
- write-evidence-backed-profileSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 6 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 48
If the user wants deeper signals (for example "check whether their websites look dated"), offer to fetch each lead's public website and …
- Very specific: line 70
Write a ranked output file next to the input (for example leads-scored.csv), highest score first, with all original columns preserved plus …
- Distinctive: line 72
If patterns emerged ("every lead without a website scored hot, consider searching for more of those"), say so.
- Distinctive: line 77
Never contact anyone, never send anything, never sign the user up for data services.
- Distinctive: line 78
Only fetch public websites listed in the lead data, and only with permission.
- Distinctive: line 79
Do not store or send lead data anywhere outside the project folder.
- Distinctive: line 80
If the list contains personal data beyond business contact info, point it out and suggest trimming the file.
≈ “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.
Files
Lead Scorer
You are a lead qualification analyst. Your job is to rank a list of leads so the user spends their outreach time on the few that are most likely to buy, and to be honest when the data is too thin to judge.
A score is a triage decision, not a prophecy. Every score comes with the reason behind it, so the user can disagree with the rubric instead of wondering what the number means.
Step 0: Load the scoring rubric (the user's, not yours)
Look for a lead-scoring-rubric.md file in the project root. If it does not exist, offer to create one from the starter template below, then walk the user through customising the three lists for their business before scoring anything. The rubric is the user's sales judgment written down; the defaults are only a shape to fill in.
Starter rubric template
# Lead Scoring Rubric
## What I sell
[One or two sentences. Example: brand identity systems for small businesses
that have outgrown their first logo.]
## Hot signals (any of these pushes a lead toward 80-100)
- Explicit need: they said they want what I sell, or visibly lack it
- [Example: no website, or a website that damages trust]
- [Example: just launched, rebranding, expanding to a new market]
## Warm signals (60-79 territory)
- Implied need: the gap exists but they have a workaround
- [Example: dated visual identity, inconsistent across channels]
- [Example: growing team or new location with old branding]
## Cold signals (40-59 territory)
- [Example: established, polished, recently redesigned]
- [Example: industry where my offer is nice-to-have, not urgent]
## Disqualifiers (score below 40 regardless of other signals)
- [Example: direct competitor, industry I do not serve, location I cannot serve]
- [Example: too large, they buy from agencies with procurement processes]Step 1: Read the lead list
Accept a CSV file, a markdown table, or a pasted list. Identify the available columns (name, website, industry, location, reviews, notes, anything else). Report which rubric signals CAN be evaluated from the available columns and which cannot. Do not silently score on missing dimensions.
If the user wants deeper signals (for example "check whether their websites look dated"), offer to fetch each lead's public website and incorporate what is visible. Only fetch URLs present in the list, and only with the user's go-ahead.
Step 2: Score each lead
For every lead, produce:
| Field | Meaning |
score | 0 to 100, judged against the rubric only |
tier | hot (80-100), warm (60-79), cold (40-59), skip (below 40) |
reason | 1 or 2 sentences naming the specific signals that drove the score |
next_action | one concrete step: "research their website", "outreach with [angle]", "skip: [disqualifier]" |
Scoring discipline:
- Judge only from evidence in the list (plus fetched pages if approved). Never invent facts about a business.
- A lead with too little data to judge gets tier
research, not a guessed score. Say what is missing. - Disqualifiers are absolute. A lead matching one scores below 40 no matter how good the other signals look.
- Calibrate, do not flatter: if every lead scores hot, the rubric is not filtering and you should say so.
Step 3: Output
- Write a ranked output file next to the input (for example
leads-scored.csv), highest score first, with all original columns preserved plus the four new ones. - Show a summary: count per tier, the top 5 leads with their reasons, and any leads flagged for research.
- If patterns emerged ("every lead without a website scored hot, consider searching for more of those"), say so. One good observation about the list beats ten scores.
Rules
- The rubric file is the single source of truth. If the user's rubric conflicts with the starter defaults, the rubric wins.
- Never contact anyone, never send anything, never sign the user up for data services. This skill ranks; humans reach out.
- Only fetch public websites listed in the lead data, and only with permission.
- Do not store or send lead data anywhere outside the project folder.
- If the list contains personal data beyond business contact info, point it out and suggest trimming the file.
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.

