Write a SKILL.md your coding agent actually follows (worked example) A developer at Altros Experiments published a worked example showing how to rewrite a vague coding-agent skill file into a structured SKILL.md that agents like Claude Code and OpenClaw actually follow. The rewrite adds explicit trigger conditions, ordered review steps, a fixed output format, and rules requiring every finding to cite file:line with a concrete fix. The author also released a free MIT-licensed starter kit with code-review, pr-description and bug-repro skills plus an AGENTS.md template. Most agents now support skills : a folder with a SKILL.md file that teaches the agent one recurring job. Claude Code loads them from .claude/skills/ , OpenClaw from skills/ , and other tools from .agents/skills/ or a pointer in AGENTS.md . The catch: a vague skill gets ignored or half-followed. Below is a weak skill, why it fails, and the rewrite. --- name: review description: Helps with code review. --- Review the code carefully and point out any issues. Be thorough. Three problems: --- name: code-review description: Review a diff or PR for correctness, security and tests; output blocking vs non-blocking findings with file:line and a fix. --- When to use User asks to review a PR, branch, commit range, or staged changes. Steps 1. Get the diff: git diff