agentleFS
nawazxznawazxz/20-claude-skills-for-business/crm-note-cleaner/SKILL.md

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.

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
  1. Distinctive:

    Read the notes and pull out the facts: who, company, what they want, budget, timeline, objections.

    line 15
  2. Distinctive:

    Write a one-line summary a manager could skim.

    line 18
  3. Distinctive:

    Only include what's in the notes.

    line 31
  4. Distinctive:

    Keep it scannable. This is a record, not prose.

    line 32

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

  1. Read the notes and pull out the facts: who, company, what they want, budget, timeline, objections.
  2. Separate facts from next steps.
  3. Note the deal stage if it's implied (e.g. discovery, proposal, negotiation).
  4. Write a one-line summary a manager could skim.
  5. 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 owners

Voice & rules

  • Only include what's in the notes. Mark anything uncertain with "(unconfirmed)".
  • Keep it scannable. This is a record, not prose.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.