crm-note-cleaner
Skill0 starsChanged 3 months agoMITView on GitHub
Turn messy call or meeting notes into a clean, structured CRM entry. Use when someone pastes rough notes from a sales call and needs them formatted for a CRM with the key fields and next steps pulled out.
In this repository19 other files it gives its agents.
- ad-copySkill
- blog-writerSkill
- cold-outreachSkill
- content-repurposerSkill
- contract-summarizerSkill
- data-cleanerSkill
- expense-summarySkill
- faq-builderSkill
- follow-up-emailSkill
- invoice-builderSkill
- lead-qualifierSkill
- meeting-notesSkill
- newsletter-writerSkill
- proposal-writerSkill
- review-responderSkill
- social-post-packSkill
- sop-writerSkill
- support-replySkill
- weekly-reportSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
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 15
Read the notes and pull out the facts: who, company, what they want, budget, timeline, objections.
- Distinctive: line 18
Write a one-line summary a manager could skim.
- Distinctive: line 31
Only include what's in the notes.
- Distinctive: line 32
Keep it scannable. This is a record, not prose.
≈ “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
CRM Note Cleaner
Convert scribbled notes into a tidy record a teammate can read at a glance.
Inputs needed
- The raw notes from the call or meeting.
- (Optional) The contact and company name if not in the notes.
Steps
- Read the notes and pull out the facts: who, company, what they want, budget, timeline, objections.
- Separate facts from next steps.
- Note the deal stage if it's implied (e.g. discovery, proposal, negotiation).
- Write a one-line summary a manager could skim.
- List clear action items with an owner if named.
Output format
Contact: name, role, company
Summary: one line
Key points: 3-5 bullets (need, budget, timeline, objections)
Stage: current deal stage
Next steps: action items with ownersVoice & rules
- Only include what's in the notes. Mark anything uncertain with "(unconfirmed)".
- Keep it scannable. This is a record, not prose.
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.

