qualify
Skill2 starsChanged 53 days agoMITView on GitHub
For leads with status new or researched, finds dated buying signals and a published contact route, records them with sources, rescores, and marks leads qualified. Use when the human types "qualify".
In this repository27 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- artifactSkill
- draft-outreachSkill
- follow-upsSkill
- knowledgeSkill
- meeting-briefSkill
- one-pagerSkill
- proposalSkill
- prospectSkill
- qualifySkill
- quote-invoiceSkill
- repliesSkill
- setupSkill
- sprintSkill
- artifactSkill
- draft-outreachSkill
- follow-upsSkill
- knowledgeSkill
- meeting-briefSkill
- one-pagerSkill
- proposalSkill
- prospectSkill
- quote-invoiceSkill
- repliesSkill
- setupSkill
- sprintSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is 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.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Search for events from the last 12 months: job posts, funding, new executives, new offices, launches, press, technology changes.
- Distinctive: line 14
Update the account file: "Why now" (date, one line, URL) and "Contact route".
- Very specific: line 19
After the batch: node tools/score.mjs --as researcher, handoff to sales, log, and a 5 line report.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
Qualify
Role: researcher. Work on node tools/leads.mjs list --status new (then --status researched),
highest score first, 10 leads per run unless the human says otherwise.
For each lead:
- Search for events from the last 12 months: job posts, funding, new executives, new offices, launches, press, technology changes. Keep only what has a date and a URL.
- Update the account file: "Why now" (date, one line, URL) and "Contact route".
- Contact route: the buyer's job title from the ICP; a named person only if published on the company's own site or a public official source; a published professional channel or the contact page. Never guess an email or pattern.
node tools/leads.mjs update <id> signals="hiring@2026-09-02; funding@2026-06-10" contact_role="..." contact_name="..." contact_channel="..." contact_source="<url>" status=qualified --as researcher- After the batch:
node tools/score.mjs --as researcher, handoff to sales, log, and a 5 line report.
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.