English | 中文
Small skills that help coding agents make better decisions: clarify before building, prove before fixing, verify before accepting, and close the loop before stopping.
I started with Superpowers. It showed me how much a structured workflow can improve agentic coding. But I also found its full spec → plan → development process too heavy for much of my daily work. Even a change of a few lines could pull in the whole ceremony.
Then I found Matt Pocock's grill-me. It was strikingly short, yet it changed the conversation in exactly the right place. That was the lesson: a skill is not valuable because it says more. It is valuable when a small instruction reliably changes an important behavior.
Astro Skills grew from that standard. I keep only the constraints that earn their place in the model's context—one recurring failure, one behavioral correction, as few tokens as the job allows.
| Skill | Use it when | What you get |
|---|---|---|
goal-writer |
You have an ambitious or long-running task, but the finish line is still vague. | A minimal execution contract that states the observable result, its acceptance criterion, and only the boundaries the task truly needs. |
shape |
Material branches of a decision tree remain unresolved, and choosing silently would change the outcome. | A shared plan you have actually agreed on, reached one consequential branch at a time. |
craft-skill |
You want to create or improve a reusable agent skill and need to know whether its instructions earn their context. | A platform-valid skill shaped through Call and Steer, with every token, evaluation, and line of code held to Earn. |
parallel-research |
A high-cost question needs broad, current, trustworthy evidence. | A faster, better-supported answer: independent evidence angles run in parallel, then the main agent cross-checks critical claims and conflicts. |
learn-anything |
You want to genuinely learn or practise something, not just receive an explanation. | Adaptive coaching that uses retrieval, application, and teach-back to build understanding you can actually use. |
tdd |
You are adding or changing production behavior and need fast, trustworthy feedback. | Small, verified increments: one predicted RED, the minimum GREEN, then safe refactoring before the next behavior. |
debug |
A bug or performance regression needs investigation, not a plausible guess. | A reproducible signal, discriminating evidence, and a root cause checked against the original symptom. |
review-feedback |
Code-review feedback may lead to changes and needs to be evaluated before acting. | An evidence-backed decision for every claim—fix, simplify, defer, or reject it at the layer that actually owns the problem. |
wrap-up |
The work is ending and you want the result finished, not merely summarized. | A closed workstream: promised outcomes verified, session-owned loose ends resolved, and the real final state reported. |
shape is the clearest example of the design. Its core is a decision tree: whenever a branch would materially change the outcome, the agent discusses that branch with the user instead of silently choosing. When the decision is genuinely visual, it renders the alternatives in HTML because seeing them is more useful than describing them.
With GitHub CLI v2.90.0 or later, install all skills for Codex:
gh skill install Astro-Han/skills --all --agent codex --scope userOr install one:
gh skill install Astro-Han/skills shape --agent codex --scope userReplace codex with your agent host, or use --scope project for a repository-local installation.
Install all skills:
npx skills add Astro-Han/skillsOr install one:
npx skills add Astro-Han/skills --skill shapeSee the Skills CLI documentation for supported agents and other options.
- Start with a failure agents actually repeat.
- Find the smallest instruction that changes that behavior.
- Keep evidence and observable outcomes; remove ceremony.
- Test demanding skills with smaller models when practical. If the skill only works because the base model is strong, the skill has not proved much.
Every line competes for limited context. If removing it does not make the agent worse at the job, it does not belong in the skill.
learn-anythingandwrap-upare original skills developed from my own workflows.craft-skilldraws from OpenAI'sskill-creator, Anthropic'sskill-creator, Matt Pocock'swriting-great-skills, and Superpowers'writing-skills. It rebuilds their strongest ideas around three constraints: call the right skill, steer the agent to genuine completion, and make every token earn its place.shapeis inspired by Matt Pocock'sgrilling. Its visual-decision rule also carries forward an idea from Superpowers'brainstormingworkflow.tddis inspired by Matt Pocock'stdd.debugdraws from Matt Pocock'sdiagnosing-bugs, Superpowers'systematic-debugging, and Waza'shunt. It deliberately reduces those approaches to a smaller evidence-driven core.review-feedbackbegan with ideas from Superpowers'receiving-code-review, but has since been substantially rewritten around evidence, ownership, scope, and system cost.
The linked projects remain the canonical sources for their skills. This repository contains my own adaptations, not vendored copies. The English SKILL.md files are the canonical instructions for Astro Skills.
MIT
