agentleFS
sharan50sharan50/Claude-Skills/.claude/skills/usage-coach/SKILL.md

usage-coach

Skill0 starsChanged 4 months agoNo licenceView on GitHub

Evaluates and coaches the user on how well they are using Claude itself — prompt quality, model choice, context engineering, task scoping, verification, and feature leverage — so they get better with every session. Use this skill whenever the user asks to review, rate, grade, critique, or improve their prompting or their use of Claude ("how could I have prompted that better?", "rate my prompt", "was that the right model?", "coach me on this session", "review how I used you"), pastes a prompt or transcript and asks what they did wrong, or asks to be coached automatically/every session. Also use it when the user has set up always-on coaching (a note in CLAUDE.md or memory referencing usage-coach) and a substantial task has just finished — that is the trigger to append a brief coaching note. Do NOT use for evaluating prompts the user is writing for other LLM apps or for grading someone else''s work.

The file

Show its rules and text

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈14

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

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

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.