agentleFS
Sign inStart free
Duckz289Duckz289/Pipeline-to-proposal-Plugin-STANDARD/skills/crm-note/SKILL.md

crm-note

Skill2 starsChanged 4 months agoMITView on GitHub

Drafts a note and task for the user to paste into their CRM, plus a stage suggestion. Triggered by "ghi lại deal này", "note cho CRM", "cập nhật CRM", "log vào HubSpot", "tạo task follow-up", "write a CRM note", "log this deal".

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 4 are distinctive, and 2 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.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If the user's environment happens to provide an approved CRM tool, it may be used — but approval is still required per …

    line 13
  2. Very specific:

    Read the deal file in <DATA>/deals/ if it exists.

    line 18
  3. Distinctive:

    Write a paste-ready note — plain text, minimal markdown, since most CRMs do not render it.

    line 20
  4. Distinctive:

    Write a follow-up task with a date.

    line 21
  5. Distinctive:

    Update the local deal file.

    line 23
  6. Distinctive:

    Use heavy markdown in the note — Salesforce and HubSpot will show raw asterisks and dashes.

    line 46

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

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

CRM note

The plugin does not write to a CRM. It prepares clean text for the user to paste.

If the user's environment happens to provide an approved CRM tool, it may be used — but approval is still required per ${CLAUDE_PLUGIN_ROOT}/policies/safety-core.md section 2.

How

  1. Read the deal file in <DATA>/deals/ if it exists.
  2. Summarise the current situation briefly.
  3. Write a paste-ready note — plain text, minimal markdown, since most CRMs do not render it.
  4. Write a follow-up task with a date.
  5. Suggest a stage change, clearly labelled as a suggestion.
  6. Update the local deal file.

Output

### Note để dán vào CRM
[Plain text, 3–5 lines: who was contacted, what they said,
what was sent, what is being waited on.]

### Task follow-up
- Hạn: 03/08/2026
- Việc: Gọi lại hỏi về phần ngân sách

### Gợi ý giai đoạn
Đề xuất chuyển sang "Đã gửi báo giá". Anh/chị tự đổi trên CRM nhé.

Headings follow the user's language.

Never

  • Say the CRM was updated when no tool actually wrote to it.
  • Change a stage in an external system.
  • Use heavy markdown in the note — Salesforce and HubSpot will show raw asterisks and dashes.

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.

Check your setup, free