Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →minpeter/minpeter-skills-maintainer
Maintains the minpeter/minpeter-skills repository — minpeter's collection of Agent Skills in the open SKILL.md format. Use this when adding a new skill there, editing or refining one, splitting an oversized SKILL.md into references/, renaming or removing a skill, or fixing drift between SKILL.md frontmatter, README.md's index table, and skills.sh.json groupings. Also use it when the user says "add a skill", "update the skills repo", or "write a skill for X". Covers the mandatory workflow (throwa
Passed 14 of 19 test cases with the skill, and 6 of 19 without it.
and 10 more in the full report
9 fixed7 passed either way6 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
I'm starting a new skill called `docker-layer-cache`. Instead of creating `skills/docker-layer-cache/SKILL.md` by hand, what CLI command should I run inside the `skills/` directory to generate the initial file and ensure valid frontmatter structure?
| Checked | Without skill | With skill |
|---|---|---|
| Scaffolds new skills using npx skills init docker-layer-cache. | Missed | Passed |
The instructions your model reads when the skill loads.
This repo is a skill collection, not an app. There is no build, no test runner, and no package.json. The "product" is a set of Markdown files that other agents load, so correctness means: valid frontmatter, discoverable descriptions, and three files that agree with each other.
This repo is public. Everything committed here is world-readable forever, and git history keeps it even after a later deletion. Treat every skill as a published document — see §4.
AGENTS.md # short house rules (keep authoritative, keep short)
README.md # install instructions + the skill index table
skills.sh.json # skills.sh repo-page groupings
skills/<kebab-name>/SKILL.md # one skill (flat layout, filename UPPERCASE)
skills/<kebab-name>/references/ # templates, deep-dives, checklists
The invariant: every skill directory has exactly one SKILL.md, and its
frontmatter name appears in both README.md's table and one
groupings[].skills array in skills.sh.json. Drift in any of the three is the
most common bug in this repo — check all three on every change.
Do not edit an existing local checkout of this repo in place, and never commit
to main. Every change — new skill, refinement, rename, removal — starts with
a throwaway clone named after the skill being touched:
SKILL=<kebab-name> # the skill you're adding or updating
KIND=skill # skill | docs | chore (see below)
BRANCH=$KIND/$SKILL # removals: BRANCH=chore/remove-$SKILL
WORK=/tmp/minpeter-skills-$SKILL
rm -rf "$WORK"
git clone https://github.com/minpeter/minpeter-skills.git "$WORK"
cd "$WORK"
test cases passed, vs 6 / 19 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.