lead-list-analysis
Skill9 starsChanged 5 months agoMITView on GitHub
Assesses the quality, composition, and usefulness of a lead list. Use when the user provides a lead list and wants completeness, distribution, quality issues, and recommended next actions.
In this repository23 other files it gives its agents.
- account-prioritizationSkill
- b2b-lead-qualificationSkill
- candidate-qualificationSkill
- company-data-normalizationSkill
- company-researchSkill
- company-research-workflow-plannerSkill
- company-segmentationSkill
- competitor-researchSkill
- directory-research-plannerSkill
- duplicate-record-reviewSkill
- job-title-normalizationSkill
- lead-list-segmentationSkill
- lead-research-workflow-plannerSkill
- market-researchSkill
- outreach-brief-generatorSkill
- partner-qualificationSkill
- persona-classificationSkill
- person-researchSkill
- prospect-list-cleanupSkill
- recruiting-sourcing-plannerSkill
- research-gap-analysisSkill
- supplier-qualificationSkill
- territory-segmentationSkill
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
- Distinctive: line 49
Do not invent missing values.
- Distinctive: line 50
Keep the analysis structure consistent.
≈ “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
Lead List Analysis
Purpose
Assess the quality, composition, and usefulness of a lead list with next actions.
When to use this skill
- Sanity-checking a list before outreach
- Measuring field completeness and gaps
- Understanding list composition
- Deciding what to fix or enrich next
When not to use this skill
- You want per-record scoring (use Lead Qualification)
- The file has no consistent structure
- You need market-level patterns (use Market Research)
Required inputs
- A lead list
Optional inputs
- Required fields for your use
- Your ICP for fit distribution
- A quality threshold
Rules
- Report real completeness rates, not estimates.
- Surface concrete quality issues with counts.
- Tie next actions to the issues found.
- Do not invent missing values.
- Keep the analysis structure consistent.
Process
- Profile the list size and fields.
- Compute field completeness.
- Summarize segment distribution.
- Detect quality issues and missing data.
- Recommend next actions.
Output format
Return a list-quality report with the following fields:
- list_overview
- field_completeness
- segment_distribution
- quality_issues
- missing_data
- recommended_next_actions
Validation
- Confirm completeness rates match the data.
- Confirm issue counts are accurate.
- Confirm actions address the issues.
Limitations
- Analysis reflects the supplied list only.
- It measures completeness, not factual correctness.
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.