ysskrishna logoysskrishna

Chapter 8 of 8 · 3 min

When a prompt should become a skill

The signals that a prompt you keep pasting deserves to be a skill, and how to convert it in ten minutes.

A prompt that works is an asset. A prompt that lives in your notes app and gets pasted by hand is a fragile asset: it drifts, teammates do not have it, and the agent cannot use it unless you remember to paste it. Skills fix that.

Five signals

Convert a prompt to a skill when:

  1. You have pasted it three or more times.
  2. Its shape is stable. You have stopped rewriting it every time. Your eval set (chapter 7) passes.
  3. Someone else needs it. A teammate asked for "that review prompt".
  4. It needs files. A template, a checklist or a script that the prompt refers to.
  5. It should trigger on its own. You want the agent to apply it whenever a certain kind of request comes up.

If only signal 1 applies, a snippet in your editor may be enough. When three or more apply, write the skill.

Converting a prompt in ten minutes

Take this prompt you have been pasting:

Review this migration. Check: locks on large tables, missing indexes on
new foreign keys, irreversible operations, default values on big tables.
Output: verdict + max 5 bullets "file:line - problem - fix".
  1. Name it after the job: migration-review.
  2. Write the description as a trigger. What would someone type? "Review this migration", "is this migration safe", "check the alembic file".
  3. Turn the checks into numbered steps.
  4. Keep the output contract exactly.
  5. Add a skip line. "Skip for application code reviews."
---
name: migration-review
description: Review a database migration for safety. Use when the user asks to review or check a migration, alembic or SQL schema change, or asks whether a migration is safe to run. Skip for application code reviews.
---

# Migration review

1. Identify each table touched and estimate its size from context; ask once if unknown.
2. Check for: long locks on large tables, missing indexes on new foreign keys, irreversible operations, defaults that rewrite big tables.
3. Output: first line APPROVE or REQUEST CHANGES; then at most 5 bullets `file:line - problem - fix`.
4. If nothing is wrong, say "No issues found." and stop.
  1. Save it to .claude/skills/migration-review/SKILL.md (or the path your host uses) and commit it.
  2. Validate with the AI Agent Skill Validator.
  3. Re-run your eval set with the skill installed instead of the pasted prompt. It should pass the same cases.

What changes after conversion

  • The agent applies the method when the request matches, without you pasting anything.
  • The team gets the same behaviour from the repo.
  • Changes go through code review, and you can version them.

When not to convert

  • One-off prompts tied to a single task.
  • Prompts that only work with lots of task-specific context; those are better as a template you fill in.
  • Behaviour that must always happen: that is a hook, not a skill (see Agent Building Blocks).

Course recap

You now have a checklist for any prompt: an outcome goal and a done-when check (1), the context only you know (2), an output contract (3), an example or two (4), a method for decisions (5), length rules (6), an eval set (7), and a path to a skill (8).

Practice: score one of your prompts

Take a prompt you have pasted at least three times this month and score it against the five signals above, one point each. Three or more points: convert it this week using the ten-minute steps. One or two points: keep it as a saved prompt or snippet and check again next month. Keeping this short habit stops your skill folder filling up with one-off prompts that never run again.

Quick check

  1. Which part of the prompt becomes the skill's trigger?None directly: you write the description as the phrases users would type when they need it.

  2. How do you know the conversion did not change behaviour?Run the same eval set with the skill and compare pass rates.

  3. "Always run the linter after edits": skill or hook?Hook. It must happen every time.

Continue exploring

CourseCover image for Agent Building Blocks: Skills, Subagents, MCP and Hooks

Agent Building Blocks: Skills, Subagents, MCP and Hooks

A free, hands-on course on the four pieces behind Cursor and Claude Code agents: skills, subagents, MCP servers and hooks. Build each one, then combine them.

Agent Skills
Chat & AI
+1

9 chapters · 30 min

BlogCover image for 17 Thinking Skills for AI Agents: Pre-Mortem, Five Whys, Six Hats and More

17 Thinking Skills for AI Agents: Pre-Mortem, Five Whys, Six Hats and More

AI Apps & Assistants
Agent Skills
4 min read
ToolCover image for AI Token Counter

AI Token Counter

AI token counter with model pricing and context-window comparison in your browser.

Chat & AI
AI Apps & Assistants
+1
Productskills.sh+1Claude Code Subagents for Cursor

Claude Code Subagents for Cursor

Your Cursor subagents can finally run on the model you picked in each agent file.
Chat & AI
Agent Skills
AI Apps & Assistants
Bash
BlogCover image for How to Install Caveman in Cursor and Claude Code

How to Install Caveman in Cursor and Claude Code

AI Apps & Assistants
Agent Skills
+1
3 min read
BlogCover image for Publish AI Agent Skills to ClawHub: Stop Re-Pasting Your AI Workflow

Publish AI Agent Skills to ClawHub: Stop Re-Pasting Your AI Workflow

AI Apps & Assistants
Agent Skills
3 min read