08of 10

Skills

Build reusable prompts. Invoke them by name.

A skill is a reusable prompt template stored where Claude can access it — most practically, in your Project Instructions or in your Settings Instructions for prompts you use across all work.

The difference between T2 and T3 is often not whether you can write a good prompt. It is whether you save the good prompts you already wrote. T2 starts from scratch. T3 invokes a template.

Creating a skill

After any prompt produces output you would use again, ask Claude to extract the pattern and format it as a named template. Copy that template into Project Instructions under a Skills header.

Using a skill

Once saved, invoke it by name: “Run Weekly Status Update on my current workstream,” or “Run Ticket Triage on this issue.” Claude reads the template and fills in the changing details.

Create a skill from a prompt that worked
Extract the reusable pattern from the prompt I just ran. Write it as a named skill template with: - A short name (3-5 words, like "Weekly Status Update" or "Ticket AC Review") - Brackets for the parts that change each time - A one-line description of when to use it Format it so I can paste it directly into my Project Instructions.

Lane examples

Dev & Build
Code Review Risk Scan

When I say 'run code review risk scan,' review the code for likely failure modes, ambiguous error handling, and one refactor that reduces risk. Output 3 items max with file/function + one-line fix.

Data & Analytics
Query Edge Case Review

When I say 'run query edge case review,' explain the query in plain language, list three edge cases, and suggest the highest-risk fix. Output as a table for technical and non-technical reviewers.

Product & Operations
Status Update

When I say 'run status update,' produce Status / Changed / Blocker / Next for the workstream I describe. Under 200 words. Lead with status. Audience: my director.

Help Desk & Support
Ticket Triage

When I say 'run ticket triage,' classify user error vs system defect, name three checks before escalation, and list what the ticket needs to be actionable for the next tier.

Build your own skill
I want to create one reusable skill for the most repetitive writing or analysis task in my work. The task I do most often is: [describe it in 2-3 sentences]. Build me a skill template for this task. Include: - A short name - The full prompt with brackets for what changes each time - One example of how I'd invoke it Format it so I can paste it directly into my Project Instructions.
Ship it (12 min)

Add one skill to your Project Instructions before the real-work exercise. You will invoke it in Tile 09.