agentleFS
RohiRIKRohiRIK/skills/CLAUDE.md

skills

CLAUDE.md1 starsChanged 30 days agoMITView on GitHub

A personal library of reusable Agent Skills. Each subfolder under skills/ is one self-contained skill (its own SKILL.md plus any supporting files). README.md is the skill index. rules/system.md is the source of truth for skill structure, the tier model (A/B/C/D), frontmatter, composition, state, and telemetry. Read it before creating or wiring skills. This file only carries the always-on essentials below. Composed chains live in workflows/ — an OKF bundle, one markdown concept per workflow (YAML frontmatter: type: Workflow, chain, tags),…

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:

    Frontmatter: every skill has name, description (WHAT + WHEN, ≤30 words), category …

    line 31
  2. Distinctive:

    README: every skill needs a row in the index.

    line 35

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

Skills — personal Agent Skills library

A personal library of reusable Agent Skills. Each subfolder under skills/ is one self-contained skill (its own SKILL.md plus any supporting files). README.md is the skill index.

Repo layout

skills/<SkillName>/   ← one folder per skill (TitleCase, matches ~/.claude/skills)
  SKILL.md           ← required: frontmatter (name, description, category, effort) + instructions
  Workflows/*.md     ← optional: execution procedures
  Tools/*            ← optional: executable scripts
  *.md               ← optional: context files (in skill root)
workflows/           ← composed skill chains, OKF bundle (one concept per workflow) — see workflows/index.md
rules/system.md      ← canonical spec for how the skill system works (READ THIS)
reports/             ← dated audit reports (reports/ModelUpgrade/<date>-<generation>.md)
_state/              ← execution-log conventions (state-file schema: skills/Iterate/StateFileSchema.md)
README.md            ← skill index
CLAUDE.md            ← this file — auto-loaded by Claude Code
AGENTS.md            ← brief for non-Claude-Code tools
INSTALL-AI.md        ← install guide
install.sh           ← symlinks skills/* into ~/.claude/skills

How the system works → rules/system.md

rules/system.md is the source of truth for skill structure, the tier model (A/B/C/D), frontmatter, composition, state, and telemetry. Read it before creating or wiring skills. This file only carries the always-on essentials below.

Conventions (essentials)

  • Folder + file naming: TitleCase. The name: field drives activation.
  • Frontmatter: every skill has name, description (WHAT + WHEN, ≤30 words), category (workflow·reference·delegation·meta·visual·prompting·quality), and effort (low·medium·high). Tier flags as needed.
  • Structure: flat, 2 levels max; only Workflows/ and Tools/ subdirs; context files in the skill root; SKILL.md ≤ 50 lines.
  • Host portability: name skills, not slash commands; capability-check host-native tools and always ship an inline fallback (see rules/system.md §7).
  • Authoring: word every skill via the Prompting skill. Reserve CRITICAL/MUST/NEVER for real gates.
  • README: every skill needs a row in the index. Adding a skill without one is incomplete.

Skill composition (always-on map)

Primitives:  Verify (quality gate) · Reflect (self-eval)
Drivers:     Iterate → calls Verify + Reflect each pass; wake primitive if the host has one, inline passes if not
             Orchestrate → Decompose→RunLayer→MergeQueue; delegates to Agy/OpenCode/Pi; gates with Verify
             Iterate:RunLenses → feeds criteria to Spec / Orchestrate
             Research → fans out to Agy/OpenCode/Pi
Meta:        SkillForge → audits + instruments the whole library;  CreateSkill → builds one skill
             ModelUpgrade → re-tunes skills for any model, current or new (Adapt | Watch → Assess → Apply; stamps tuned-for per family)
Wired in:    Build→Verify · Test→Reflect · Spec --deep→Iterate:RunLenses · Agy/OpenCode/Pi→.agent-state.md on failure
State:       loop/multi-pass skills share .agent-state.md
Telemetry:   action workflows append to ~/.claude/state/execution.jsonl

Composed chains live in workflows/ — an OKF bundle, one markdown concept per workflow (YAML frontmatter: type: Workflow, chain, tags), two families: build & ship (ship-fast, spec-to-ship, research to build/report/buy, onboard, build-cli/mcp, ui/api-feature, security/context/hygiene passes) and maintain the library (new-skill, canonicalize, fix-trigger, autonomous-loop, batch-build, library-audit, model-upgrade, release). See workflows/index.md for the index.

Source of truth

This repo is canonical. Skills are symlinked into ~/.claude/skills by install.sh; edits flow through the symlink back here. Run install.sh after cloning to onboard a new machine.

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.