skills

Skills for Claude Code, kept in one place so a second machine gets the same
ones and so a change to any of them has a history.

They were installed by hand into ~/.claude/skills/, which is not a
repository, which meant they existed on exactly one disk. That is what this
fixes.

Installing

/plugin marketplace add productdevbook/skills
/plugin install productdevbook-skills@productdevbook

What is in it

Skill	For
rust-guidelines	Designing Rust: the shape of a public API, how an error type is built, whether to split a crate, what goes on a hot path, how a workspace is laid out. Read before writing.
apollo-rust-review	Judging Rust that already exists: ownership and clone discipline, clippy policy, errors at crate vs binary boundaries, tests as documentation, pointers. Carries a P0–P3 severity matrix and a set of rejection triggers. Read when reviewing.
sentry-cli	Driving Sentry from the command line — issues, events, releases, the API.
agent-briefs	Setting up a multi-agent run: role files that carry the reason rather than a checklist, briefs that separate what is decided from what the agent must decide, and which claims to verify before believing them. Read when the same instruction keeps being repeated in every task.
ratchets	Finding the bugs that reading code does not find, and writing the tests that stop each one coming back. Counting callers rather than judging quality; tolerated lists that may only shrink; what a check must not claim. Read when a bug has been fixed twice.

The two Rust skills overlap on purpose and their descriptions say which is
which: one designs a surface, the other judges a diff. Keep that distinction
in the descriptions if either is edited, or the wrong one gets opened.

Where they came from

Both Rust skills are derived from other people’s work and keep their licences:

• rust-guidelines — 89 rules from
  microsoft/rust-guidelines,
  Copyright © Microsoft Corporation, MIT.
• apollo-rust-review — from
  apollographql/rust-best-practices,
  Apache-2.0. The licence travels with it in
  skills/apollo-rust-review/LICENSE, and the nine chapters of the book are
  under references/. The upstream repository ships this as a Codex-format
  skill; here the body is kept and the front matter rewritten so that Claude
  knows when to open it, and so that it does not collide with the Microsoft
  one.

Nothing here is original work beyond the packaging and the descriptions.

Editing one

A skill is a directory with a SKILL.md and whatever it needs beside it. The
front matter’s description is the only part that is always in context — it
is what decides whether the skill is opened at all, so it should say when
to reach for it, not only what it contains. The body is read once the skill is
opened, and anything long belongs in references/, read on demand.