agent-skills
CLAUDE.md72 starsChanged 6 months agoMITView on GitHub
Contributor guide for this skills library when working in Claude Code. The marketplace name is dgalarza-agent-skills. The GitHub repository is dgalarza/agent-skills. It was renamed from dgalarza/claude-code-workflows. Do not create a repository with the old name, because that breaks GitHub's redirect. Architecture and the reasons for the layout are in ARCHITECTURE.md. AGENTS.md is the same guide for other agents. Claude Code plugins are codebase-readiness, agent-ready, and engineering-skills. herdr-code-review (an engineering skill outside the bundle) and the operator utility buffer stay under…
- Commits and pushes
In this repository13 other files it gives its agents.
- AGENTS.mdAGENTS.md
- skill-creatorSkill
- agent-readySkill
- bufferSkill
- codebase-readinessSkill
- code-snippetSkill
- conventional-commentsSkill
- conventional-commitsSkill
- herdr-code-reviewSkill
- stacked-prsSkill
- tddSkill
- team-code-reviewSkill
- webhook-receiverSkill
The file
We split this CLAUDE.md into the rules it gives an agent
8 rules. About 0 are common, 2 are distinctive, and 6 are 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.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 36
Commit messages follow conventional commits: feat:, fix:, chore:, docs:.
- Very specific: line 40
Add or edit the skill under skills/<name>/.
- Very specific: line 64
Commit the version bump with the change, or as chore: bump <plugin> to YYYY.MM.PATCH.
- Distinctive: line 65
After the merge to main:
- Distinctive: line 72
Create a GitHub release from the tag with a short summary.
- Very specific: line 78
Create skills/<name>/SKILL.md with frontmatter and instructions.
- Very specific: line 80
Add a short row to the matching group in README.md and INSTALL.md.
- Very specific: line 81
Leave operator utilities out of .claude-plugin/marketplace.json.
≈ “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.
Files
Agent Skills
Contributor guide for this skills library when working in Claude Code. The marketplace name is dgalarza-agent-skills. The GitHub repository is dgalarza/agent-skills. It was renamed from dgalarza/claude-code-workflows. Do not create a repository with the old name, because that breaks GitHub's redirect.
Architecture and the reasons for the layout are in ARCHITECTURE.md. AGENTS.md is the same guide for other agents.
Repository Structure
skills/<name>/
SKILL.md # Canonical skill (required)
scripts/ # Executable code (optional)
references/ # Docs loaded into context as needed (optional)
assets/ # Templates and files used in output (optional)
plugins/<plugin-name>/
.claude-plugin/plugin.json # Thin manifest: name, version, description, author
README.md # User-facing plugin docs
skills/<name> # Symlink to ../../../skills/<name>
tests/ # Tests of that plugin's templates, when present
.claude-plugin/marketplace.json
.agents/skills/ # Vendored skill-creator used by CI. Not a published skillClaude Code plugins are codebase-readiness, agent-ready, and engineering-skills. herdr-code-review (an engineering skill outside the bundle) and the operator utility buffer stay under skills/ and are installed with npx skills only.
Symlinks stay inside this repository. Claude Code dereferences a symlink whose target is another directory in the same marketplace and copies that content into the plugin cache.
Key Conventions
- Plugin versions live in
plugins/<name>/.claude-plugin/plugin.jsonand in.claude-plugin/marketplace.json(the plugin entry and the marketplaceversion). Keep them in sync. - Versions use calendar versioning:
YYYY.MM.PATCH(this consolidation is2026.10.0). IncrementPATCHfor later changes in the same month. - SKILL.md frontmatter requires
name(kebab-case, max 64 characters) anddescription(max 1024 characters, no angle brackets). - Skill instructions use imperative or infinitive form.
- Skill steps that can run in parallel must also say what to do when the runtime has no subagents.
- JSON files must be valid. CI checks this.
- Commit messages follow conventional commits:
feat:,fix:,chore:,docs:.
Development Workflow
- Add or edit the skill under
skills/<name>/. - For a Claude plugin, point
plugins/<plugin>/skills/<name>at../../../skills/<name>and list the plugin in.claude-plugin/marketplace.json. - Validate locally:
python3 .agents/skills/skill-creator/scripts/quick_validate.py skills/<name> - CI validates skills and JSON on pull requests.
- Bump the CalVer version in both plugin.json and marketplace.json before merging behavior changes.
Releasing
Git tags for the marketplace snapshot stay YYYY.MM.DD. If more than one tag lands on the same day, append a suffix: YYYY.MM.DD.2. Plugin and marketplace versions stay YYYY.MM.PATCH.
When to Release
Cut a release when one or more of these land on main:
- New plugin or skill added
- New feature or language support added to an existing skill
- Bug fix that affects skill or plugin behavior
Documentation-only changes do not need a release.
Release Checklist
- Bump the plugin version in
plugins/<name>/.claude-plugin/plugin.jsonusingYYYY.MM.PATCH. - Set the same version on that plugin's entry and on the top-level
versionin.claude-plugin/marketplace.json. - Commit the version bump with the change, or as
chore: bump <plugin> to YYYY.MM.PATCH. After the merge to
main:git tag YYYY.MM.DD git push origin YYYY.MM.DD- Create a GitHub release from the tag with a short summary.
Retired plugin names stay in the marketplace renames map. Map a removed plugin to null. Map a plugin that moved into another plugin to that plugin's name. Keep old renames entries when adding new ones.
Adding a Skill
- Create
skills/<name>/SKILL.mdwith frontmatter and instructions. - To ship it in Claude Code, add a symlink under the right plugin and a marketplace entry.
- Add a short row to the matching group in
README.mdandINSTALL.md. - Leave operator utilities out of
.claude-plugin/marketplace.json.
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
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.

