Skip to content
Matthew Blode
Guide

Chapter 3 of 6

Turn prompts into skills

If I repeat a prompt, it becomes a skill.

A prompt handles the job in front of me. An agent skill handles the part I expect to repeat.

When I notice myself giving the same correction, I move it into a `.md` file. Review checklists, UI audits, tone, release steps, and PR monitoring all started that way. No API, no SDK, no build.

The skill carries the judgement: what to inspect, which commands to run, what to cut, and when to stop. My prompt can stay short because the skill already knows the routine.

I use narrow skills for separate passes. `ui-design` makes the interface pass. `tidy` simplifies the diff. `visual-qa` checks the real screen. `pr-babysitter` stays with the pull request until it lands.

Run `npx skills add mblode/agent-skills` and those habits follow the agent. An MCP gives it a tool. Repo instructions add the local rules.

Read the long version: Skills are the new packages · Agent Skills