agentleFS
CSPulseCSPulse/customer-success-skills/skills/cs-start/SKILL.md

cs-start

Skill2 starsChanged 3 months agoMITView on GitHub

Use when the user says "customer success", "help with my accounts", "where do I start", "what can you do for a CSM", "I'm a CSM", "I lead a CS team", "run the demo", "show me what this does", or is unsure which customer success skill fits. Routes any situation to the right skill and runs it, shows a 60 second demo on an invented account, and anonymizes any output so it is safe to share. Not for doing the work itself (the routed skill does that).

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

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

    If the user described a situation (a call, an account, a number, a message they dread sending), match it against references/routes.md, say …

    line 13
  2. Distinctive:

    If they said nothing specific, or said "demo", "show me" or "what can you do", ask this ONE question:

    line 15
  3. Very specific:

    Route: Use the table in references/routes.md.

    line 26
  4. Distinctive:

    Check it is installed: If the routed skill is not available in this session, do the job directly with the same principles (verdict first, …

    line 27
  5. Very specific:

    When the user picks 5 or asks for a demo, load references/demo.md.

    line 33
  6. Distinctive:

    When the user says "make this shareable", "anonymize this", "remove names" or "I want to post this", rewrite the last output with:

    line 37
  7. Distinctive:

    Never post, upload or send it anywhere.

    line 44
  8. Distinctive:

    One question at most: If the first answer is enough to route, route.

    line 51
  9. Distinctive:

    Every other skill in the library.

    line 55

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

CS Start

The front door. One question, then straight into the right skill. If the user already described a situation, skip the question and run the skill.

Start here

If the user described a situation (a call, an account, a number, a message they dread sending), match it against references/routes.md, say in one line which skill you are using, and run it. Do not ask which skill they want.

If they said nothing specific, or said "demo", "show me" or "what can you do", ask this ONE question:

What is in front of you right now?

  1. A call or meeting (coming up, or just finished)
  2. One account I am worried about, renewing, or inheriting
  3. Something I have to write or say to a customer
  4. My whole book or my team's numbers
  5. Show me a 60 second demo

Do this

  1. Route. Use the table in references/routes.md. Pick the single best skill. If two fit, pick the one closer to the user's next action and mention the other as the follow-up.
  2. Check it is installed. If the routed skill is not available in this session, do the job directly with the same principles (verdict first, evidence tagged, gaps named) and tell the user the named skill exists in the library.
  3. Run it. Hand over with no preamble. The user's situation is the input.
  4. Offer the next step once. One line, naming the follow-on skill and what it would produce.

Demo mode

When the user picks 5 or asks for a demo, load references/demo.md. Run renewal-risk on the invented Marlowe Freight account in it, show the output, then say: "Paste your own account in the same three lines and I will do the real one."

Share-safe mode

When the user says "make this shareable", "anonymize this", "remove names" or "I want to post this", rewrite the last output with:

  • Customer, vendor, person and product names replaced by consistent invented ones
  • Dollar figures scaled by one consistent factor and dates shifted by one consistent offset
  • Quotes paraphrased unless they contain nothing identifying
  • A final line: Anonymized. Check it once more before posting.

Never post, upload or send it anywhere.

Rules

  • Route on the situation, not the keywords. "They want a discount" is renewal-negotiation even though the user never said negotiation.
  • Do not make the user learn the library. Names of skills are for the model; the user speaks in situations.
  • Persona is a hint, not a gate. A CSM can run a leader skill and the reverse. If the user says "I lead a team", start from references/routes.md section B or C but still match on the situation.
  • One question at most. If the first answer is enough to route, route.

Related (only if installed)

Every other skill in the library.

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.