agentleFS
cobusgreylingcobusgreyling/grok-bot-templates/skills/rank-account-health/SKILL.md

rank-account-health

Skill14 starsChanged 3 months agoMITView on GitHub

Paste this into Grok Bot after a successful run: Save the process we just used as a skill called “Rank Account Health”. A useful skill states the six fields from Skills and routines. A customer portfolio needs a ranked watch list from usage, support, renewal timing, and stakeholder activity — evidence, not a feeling. Every rank has a threshold citation. No customer is emailed. CRM is not edited. Ranked watch list with evidence links, suggested next step, and a "needs…

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    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:

    Write evidence, why it matters, and a suggested next step.

    line 24
  2. Distinctive:

    Every rank has a threshold citation.

    line 29
  3. Distinctive:

    Do not contact customers. Do not edit the CRM.

    line 39

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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

Rank Account Health

Paste this into Grok Bot after a successful run:

Save the process we just used as a skill called “Rank Account Health”.

A useful skill states the six fields from Skills and routines.

1. When to use it

A customer portfolio needs a ranked watch list from usage, support, renewal timing, and stakeholder activity — evidence, not a feeling.

2. Required inputs and access

  • Account list or CRM segment
  • Risk thresholds (ask once if missing — usage drop, open P1s, days to renewal)
  • Support, billing, and success notes the owner approved as sources

3. Sequence of work

  1. Load current data. If a source is down, name it and continue with what you have — never substitute last week's file silently.
  2. Score each account against the saved thresholds.
  3. Write evidence, why it matters, and a suggested next step.
  4. Rank. Separate expansion signals from churn signals.

4. How to validate the result

Every rank has a threshold citation. No customer is emailed. CRM is not edited.

5. What to return

Ranked watch list with evidence links, suggested next step, and a "needs human" flag.

6. What requires approval

Do not contact customers. Do not edit the CRM. Do not issue refunds or credits.

Type / in the composer to reference a saved skill. If it does not appear, open Settings → Plugins → Yours and enable it for this Bot.

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.