prospect-list-cleanup
Skill9 starsChanged 5 months agoMITView on GitHub
Normalizes and improves the consistency of prospect-list data. Use when the user provides a messy prospect or lead export and wants standardized records, flagged issues, and a cleanup summary.
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-analysisSkill
- lead-list-segmentationSkill
- lead-research-workflow-plannerSkill
- market-researchSkill
- outreach-brief-generatorSkill
- partner-qualificationSkill
- persona-classificationSkill
- person-researchSkill
- recruiting-sourcing-plannerSkill
- research-gap-analysisSkill
- supplier-qualificationSkill
- territory-segmentationSkill
The file
Files
Prospect List Cleanup
Purpose
Normalize and improve the consistency of prospect-list data before outreach or import.
When to use this skill
- Preparing an export for CRM or outreach import
- Standardizing names, casing, and formats
- Flagging incomplete or broken rows
- Producing a defensible cleanup audit
When not to use this skill
- You need verified emails or enrichment, not cleanup
- The file has no consistent columns to normalize
- You want hard de-duplication (use Duplicate Record Review)
Required inputs
- A prospect or lead list
Optional inputs
- A target column schema
- Formatting conventions (casing, phone format)
- Fields that are mandatory
Rules
- Standardize formatting; do not invent missing values.
- Flag incomplete and suspect rows rather than deleting them.
- Record every change in normalization notes.
- Preserve the original value when flagging an error.
- Apply the same conventions to every row.
Process
- Profile the columns and detect formats.
- Normalize casing, names, companies, and formats.
- Flag incomplete and suspected-error rows.
- Record normalization notes.
- Produce a cleanup summary with counts.
Output format
Return the cleaned list plus a summary with the following fields:
- standardized_records
- incomplete_records
- suspected_errors
- normalization_notes
- cleanup_summary
Validation
- Confirm no values were invented.
- Confirm flagged rows retain their original data.
- Confirm the summary counts match the records.
Limitations
- It standardizes formatting, not factual accuracy.
- Suspected errors are heuristics and should be reviewed.
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.

