agentleFS
Sign inStart free
Soul-Brews-StudioSoul-Brews-Studio/skills/CLAUDE.md

skills

CLAUDE.md0 starsChanged 2 months agoMITView on GitHub

Public repo of standalone agent skills, installable via npx skills@latest add Soul-Brews-Studio/skills. skills/<category>/<skill-name>/SKILL.md — one self-contained file per skill. .claude-plugin/plugin.json lists every skill path; marketplace.json makes the repo an installable Claude Code plugin marketplace. 1. skills/<category>/<name>/SKILL.md with YAML frontmatter (name, description, optional argument-hint) 2. Add "./skills/<category>/<name>" to .claude-plugin/plugin.json 3. Add a section to README.md 4. Verify: npx skills@latest add ./ --list - Public repo. No secrets, no internal hostnames, no personal emails, no private-repo paths. Scan before every push. -…

The file

We split this CLAUDE.md into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

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

    Add "./skills/<category>/<name>" to .claude-plugin/plugin.json

    line 16
  2. Distinctive:

    Add a section to README.md

    line 17
  3. Distinctive:

    Public repo: No secrets, no internal hostnames, no personal emails, no private-repo paths.

    line 22

≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.md 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
CLAUDE.md

Soul Brews Studio — Skills

Public repo of standalone agent skills, installable via npx skills@latest add Soul-Brews-Studio/skills.

Layout

skills/<category>/<skill-name>/SKILL.md — one self-contained file per skill. .claude-plugin/plugin.json lists every skill path; marketplace.json makes the repo an installable Claude Code plugin marketplace.

Adding a skill

  1. skills/<category>/<name>/SKILL.md with YAML frontmatter (name, description, optional argument-hint)
  2. Add "./skills/<category>/<name>" to .claude-plugin/plugin.json
  3. Add a section to README.md
  4. Verify: npx skills@latest add ./ --list

Rules

  • Public repo. No secrets, no internal hostnames, no personal emails, no private-repo paths. Scan before every push.
  • Rule 6. Skills that invoke real people name them as influences and never write first person as them. Never a fabricated quote.
  • Self-contained. A skill is one SKILL.md. If it needs scripts, it doesn't belong here yet.

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