agentleFS
Sign inStart free
joestumpjoestump/claude-skills/CLAUDE.md

claude-skills

CLAUDE.md2 starsChanged 6 months agoMITView on GitHub

Mono-repo of personal Claude skills. Each top-level directory (other than .github/) is one self-contained skill with its own SKILL.md, references, and assets. Skills version independently using per-skill tags: The release workflow (.github/workflows/release-skill.yml) parses the skill name from the tag, zips that directory, and attaches <skill-name>.zip to a GitHub Release. GitHub Actions handles the rest.

  • Commits and pushes

The file

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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:

    Don't use a global v* tag — skills are unrelated and shouldn't share a version.

    line 23
  2. Distinctive:

    Follow semver: breaking changes to a skill's contract bump MAJOR, additive changes MINOR, fixes PATCH.

    line 24

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

claude-skills

Mono-repo of personal Claude skills. Each top-level directory (other than .github/) is one self-contained skill with its own SKILL.md, references, and assets.

Versioning & tagging

Skills version independently using per-skill tags:

<skill-name>-v<MAJOR>.<MINOR>.<PATCH>

Examples:

  • retirement-plan-v1.0.0 — first stable release of the retirement-plan skill
  • retirement-plan-v1.1.0 — added a tab or knob
  • retirement-plan-v1.1.1 — bug fix in the template

Rules:

  • Tag from main after the change is merged.
  • One skill per tag. Don't bundle multiple skills into one tag.
  • Don't use a global v* tag — skills are unrelated and shouldn't share a version.
  • Follow semver: breaking changes to a skill's contract bump MAJOR, additive changes MINOR, fixes PATCH.

The release workflow (.github/workflows/release-skill.yml) parses the skill name from the tag, zips that directory, and attaches <skill-name>.zip to a GitHub Release.

Cutting a release

git tag retirement-plan-v1.2.0
git push origin retirement-plan-v1.2.0

GitHub Actions handles the rest.

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