--- title: "Skills and Commands: Reusable Superpowers" description: "Package recurring workflows into reusable skills and slash commands you can trigger instantly, and know when each is worth building" type: "lesson" locale: "en" course: "Claude Code Mastery - Becoming a Power User" number: "2.2" canonical: "https://agenticschool.dev/courses/claude-code-mastery/skills-and-commands-reusable-superpowers" datePublished: "2026-06-12" dateModified: "2026-06-12" --- # Skills and Commands: Reusable Superpowers - Course: Claude Code Mastery - Becoming a Power User - Lesson: 2.2 - Duration: 23 min - Level: einsteiger - Status: published - Canonical URL: https://agenticschool.dev/courses/claude-code-mastery/skills-and-commands-reusable-superpowers - Locale: en > Package recurring workflows into reusable skills and slash commands you can trigger instantly, and know when each is worth building ## Summary Once you catch yourself giving the agent the same multi-step instructions twice, you should package them. Slash commands and skills turn a proven workflow into a single reusable trigger, so the agent does complex, consistent work without you retyping the brief. This lesson shows what a SKILL.md file really is, how it differs from a slash command, and how to build a small personal library that matches how you actually work. ## What you learn - What a SKILL.md file is, what a slash command is, and when to reach for each - Packaging a proven multi-step workflow so it runs consistently every time - Building a small, focused library of skills you will actually remember and use ## Summary Skills and slash commands are reusable, named workflows. Instead of describing the same task from scratch every time, you invoke one and the agent runs your proven steps with your context already loaded. A slash command is a quick trigger for a prompt you reuse. A skill is a richer, self-contained capability the agent can pull in when it is relevant. Both are how you stop retyping your best workflows and start banking them as permanent assets in the repo. ## What you will learn You will learn the concrete difference between a slash command and a skill, what actually lives inside a SKILL.md file including its frontmatter, how to capture a workflow you keep repeating, and how to build a focused library of two or three skills that fit your own way of working rather than a sprawling collection you forget about. ## Prerequisites A working Claude Code setup and a CLAUDE.md from the previous lesson, because skills and commands build on the conventions defined there - a skill that scaffolds a component should obey the same naming and style rules your project file already states. ## The problem You have a workflow you trust. Maybe it is "scaffold a new page, add it to the router, write a smoke test, run the quality gate". You type the same paragraph briefing it every time, slightly differently, and you get slightly different results. The knowledge is in your head and your fingers, not anywhere reusable. When you are tired you forget a step. When a teammate does it, they do it their own way. The workflow is real and proven, but it is not captured, so it is fragile and inconsistent. ## Slash commands: a reusable prompt A slash command is the simplest form of reuse: a markdown file containing a prompt you invoke by typing a slash and its name. Drop a file in the commands folder and Claude Code exposes it as a command. It is perfect for a single, well-defined action you trigger often - run the quality gate, open a PR with your standard description, summarise what changed since the last commit. The file can take arguments, so one command flexes across cases. Reach for a command when you want speed and a single clear action. ```markdown --- description: Run the full pre-push quality gate and report failures clearly. --- Run these in order and stop at the first failure: 1. bun run lint 2. bun run typecheck 3. bun run test If anything fails, show me the exact error and the file it points to, then propose the smallest fix. Do not push. ``` A slash command at .claude/commands/ship-check.md, invoked as /ship-check ## Skills: a packaged capability A skill is more than a prompt. It is a folder with a SKILL.md file at its root, carrying frontmatter (a name and a description) plus instructions, and optionally bundled scripts, templates or reference files the agent can use. The description matters enormously: the agent reads it to decide when the skill is relevant and pulls the skill in automatically, so a sharp description is what makes a skill discoverable. Use a skill when a workflow is multi-step, has its own context or assets, and benefits from being a self-contained unit you maintain in one place. Here is a real SKILL.md frontmatter and body for a component-scaffolding skill. ```markdown --- name: new-component description: Scaffold a new React component with its test and story. Use when the user asks to create, add or scaffold a component. --- # New Component When creating a component: 1. Create the component in src/components as a PascalCase .tsx file. 2. Use rounded-sm and the existing button/card styles - never invent new tokens. 3. Create a colocated .test.tsx with a render smoke test. 4. Export it from the components barrel file. 5. Run bun run typecheck on just the new files and fix any errors. Follow all rules in the project CLAUDE.md. Never add a new UI dependency. ``` A real SKILL.md: frontmatter (name, description) plus instructions ## Capturing a workflow and choosing the form The signal to package something is simple: the second time you brief the agent on the same sequence, that sequence is a candidate. Write the steps down once. Then choose the form by asking how rich it is. A single clear action with no assets is a slash command. A multi-step process with its own context, templates or bundled scripts is a skill. Do not overthink it - you can start with a command and promote it to a skill later when it grows. The win is capturing the workflow at all, the same continuous-learning habit from the last lesson applied to processes instead of rules. - Repeated twice = candidate for packaging. Do not wait for the tenth time. - Single action, no assets, want speed: slash command. - Multi-step, own context or bundled files, want a self-contained unit: skill. - A great skill description is half the work - it is how the agent knows when to use it. ## A focused personal library Start small and deliberate. Two or three skills and commands for the workflows you do most - your quality gate, scaffolding a component, opening a standard PR - beat a sprawling collection of twenty you half-remember. A focused library is one you actually reach for, and every entry earns its place by saving you a real, repeated briefing. As with the rules file, prune what you stop using and promote what you keep pasting by hand. The goal is not maximum skills, it is maximum leverage per skill. ## Typical mistakes The usual traps: building a skill before you have run the workflow enough to know the right steps, so you bake in a bad process; writing a vague skill description so the agent never figures out when to invoke it; hoarding dozens of skills you forget exist; and duplicating logic that already belongs in CLAUDE.md. Skills are for workflows, the rules file is for standards - keep them in their lanes. ## Business ROI A packaged workflow is a process that no longer depends on the person who invented it. Your best way of scaffolding, testing or shipping becomes a one-word trigger that runs the same way for you, for a teammate, and for a contractor on day one. That is how a small team punches above its weight: the founder encodes the right way to do something once, and everyone runs it consistently forever. Inconsistent processes are a silent tax on quality, and a small skills library removes it for the price of a few markdown files. ## Checklist You are ready to move on when each of these is true. The next lesson automates the checks these workflows often end with. - You can explain when a slash command beats a skill and vice versa. - You have written at least one slash command for a workflow you repeat. - You can describe what lives in a SKILL.md, including why the description matters. - Your library is small and focused, not a pile of unused entries. ## Resources Bookmark the official Claude Code docs on skills and slash commands for the exact folder locations and frontmatter fields, which evolve over time. The resource library has a starter pack of command and skill templates you can copy. Pair every skill with your CLAUDE.md so packaged workflows automatically inherit your project standards. ## Your task Pick the one workflow you brief the agent on most often. Write it as a slash command first - just the prompt in a markdown file in your commands folder. Invoke it twice on real work. If it grows steps or needs its own assets, promote it to a skill with a sharp description. You now have your first reusable superpower banked in the repo. ## Next lesson Skills and commands run when you trigger them. The next lesson goes one level further: hooks and scripts that run automatically at key moments, so your quality gates fire without you ever remembering to invoke them. ## Transcript This lesson is a written, text-first guide. Once you catch yourself giving the agent the same multi-step instructions twice, you should package them. Slash commands and skills turn a proven workflow into a single reusable trigger, so the agent does complex, consistent work without you retyping the brief. This lesson shows what a SKILL.md file really is, how it differs from a slash command, and how to build a small personal library that matches how you actually work. You will package recurring workflows into reusable skills and slash commands you can trigger instantly, and know when each is worth building. Work through the sections in order, try the task at the end in a real project, and move on once it works for you. There is no video required - everything you need is in the written steps above.