contact-qualifier
Skill16 starsChanged 49 days agoApache-2.0View on GitHub
Score sourced contacts against the ICP and tier them QUALIFY / MAYBE / SKIP so paid enrichment is spent only on good-fit contacts. Context-driven (segments.md rubric + personas.md + exclusions.md); no provider, no credits. Always includes a human review gate. Use when the user wants to "qualify the list", "score these contacts", or run only the qualify stage.
In this repository10 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- activateSkill
- company-discoverySkill
- company-enricherSkill
- contact-sourcerSkill
- email-finderSkill
- gtm-setupSkill
- gtmSkill
- phone-finderSkill
The file
Files
Input (list_id, optional thresholds/overrides): $ARGUMENTS
Execute the qualifier: read agents/contact-qualifier/agent.md and follow it exactly —
bootstrap (config + personas.md + segments.md + exclusions.md), load sourced contacts
via storage/cli.py query_by_stage, apply exclusions, classify company segment, match
persona, score 0–10 per the context rubric, present the QUALIFY/MAYBE/SKIP review (Gate
#2) for human sign-off, then advance_stage to qualified (or skipped). Report the
tier/segment/persona breakdown.
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.

