agentleFS
CSPulseCSPulse/customer-success-skills/template/SKILL.md

skill-name

Skill2 starsChanged 3 months agoMITView on GitHub

Use when the user says "literal phrase one", "literal phrase two", "literal phrase three", or describes [the situation in plain words]. [One sentence on what it produces.] Not for [adjacent job] (use sibling-skill).

39 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use git-workflow and frontend-design.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • Microsoft AzureSkill

    git-workflow

    Squad branching model: dev-first workflow with insiders preview channel

    Also in 3 projects that use this

  • BlockSkill

    frontend-design

    Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 17 edited versions we read keep these.

  • 1

    Distinctive

    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:

    If the user has already given [the minimum input], go straight to "Do this".

    line 13

“Common” is measured: kept by at least 6 in 10 of the 17 edited versions of this file we could read. “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

Skill Name

One sentence: what the user walks away with.

Start here

If the user has already given [the minimum input], go straight to "Do this".

Otherwise ask for these in ONE message, then proceed with whatever comes back. Never wait for a complete answer:

  1. [Input 1, the one that changes the answer most]
  2. [Input 2]
  3. [Input 3]

Anything missing becomes a line under "What I could not check", not a reason to stop.

Do this

  1. [Imperative step, one to three lines.]
  2. [Imperative step.]
  3. [Imperative step.]

Six steps at most. If a step needs more than a screen of explanation, move the detail to references/ and say when to load it.

Output

Lead with the verdict or the thing the user will send. Use this skeleton exactly:

[Headline: the call, the draft, or the one-line answer]

[Block 1]
[Block 2]

What I could not check
- [gap 1]
- [gap 2]

A filled example is in examples/sample.md. Match its shape and length.

Rules

Five to eight judgement rules, each with the mechanism behind it. This is where the skill earns its place over a plain prompt.

  • [Rule]. [Why it is true.]

Related (only if installed)

One line: which sibling skill to suggest next, and when. Suggest, never require.

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.