Skills
Agent skills I actually use, grouped by purpose. Each group is independent — install a whole group, or just the skills you want.
Skills that only make sense inside my own workflow live in a separate private repo; everything here works for anyone.
Install
Everything:
npx skills@latest add BCGen/skills
One group, or a few skills by name:
npx skills@latest add BCGen/skills -s retro codify
Update later:
npx skills@latest update
Agent harness & skill authoring
Skills that make an agent learn from a project and from its own mistakes. A coherent set — read the full story.
In scope: capturing conventions, routing lessons into durable rules, and auditing skills. Out of scope: anything tied to one language, framework, or product.
| Skill | What it does | When to use it |
|---|---|---|
| harness-sync | Sets up and re-syncs the entry-file harness block that wires retro in, plus cross-agent interop glue. | Run at setup to make retro fire reliably and unify agents on one source; re-run after a skills update to re-sync the managed block. Optional — everything also bootstraps without it; retro owns the loop. |
| codify | Captures a project's existing conventions so the agent follows them from the first run. | First on an existing project, before the agent's first real task. Re-run as things evolve — it reconciles, never duplicates, and proposes upgrades when placed artifacts fall short of current standards. |
| retro | After a task, turns your corrections into durable improvements, with your consent. | At the end of every task — especially one where you corrected the agent. Saying done or wrap up triggers it too. |
| rule-writing | The one place rules get written — filtered, budgeted, provenance-stamped. | Mostly invoked by codify/retro handing it drafts; call it directly when you already know a landmine worth a rule. |
| skill-auditing | Audits a skills directory for stale format or facts. | Periodically, or when a skill seems outdated. |
Writing a skill
We don't ship one for this. Claude understands the SKILL.md format natively — ask it to write one. The tools worth reaching for are already out there:
| grilling | One question at a time, each carrying a recommended answer for you to push against. The hardest part of writing a skill is getting the procedure out of a human's head. |
| writing-great-skills | A style reference — the vocabulary that makes a skill predictable. |
| skill-creator | Anthropic's own. Evals against a baseline, benchmarking, description tuning — for when you want the draft measured rather than trusted. |
Contributing
Development setup and the spec workflow are in CONTRIBUTING.md.
No comments yet
Be the first to share your take.