Stop re-explaining yourself every session. Build one Skill today that does the work for you — every time, without the brief.
A Skill is a recipe Claude follows every time you trigger it. Write your rules once. Use them forever. Here's why that's such a quiet superpower.
Your tone guide, your framework, your "never do this" list. Loaded every time. You stop being a one-person prompt library.
That one great newsletter? That's now the template. The deliverable becomes the recipe.
Your voice guide feeds your hook generator feeds your repurposer. Each Skill makes the next one faster.
The closest thing to handing a task to a team member who actually reads the brief. Every time.
Not a marketplace template. Not someone else's prompt. Built around how you actually work.
You'll have one done in under 30 minutes today. No code. No setup. Just thinking.
If you do something five or more times, regularly — it should be a Skill. Not a saved prompt. Not a sticky note on your monitor. A Skill. Because the third time you re-write that brief, you've lost the morning.
Three things that get muddled. Here's the difference, in one breath each.
You ask. It answers. Then it's gone. Great for tinkering. Bad for repeatable work.
A folder of context — files, docs, knowledge. Claude reads from it across many chats.
Standing instructions. Triggered by a phrase. Runs the same steps every single time. This is what you want for the work that repeats.
Five parts. That's it. Once you can see the shape, you can build one for almost anything.
The mistake everyone makes: jumping straight to "write me a Skill that does X." Claude needs you to think first. Open Cowork — where you already set up your folder last workshop — and use the built-in skill-creator to interview you. Five minutes here saves an hour of building the wrong thing.
Cowork's skill-creator is a meta-Skill that builds other Skills. You describe the outcome. It asks the questions. It packages everything for you. No code. No syntax to learn.
Last workshop you set up Cowork. Today, Cowork is also where you build the Skill — using the skill-creator. Once installed, Skills work everywhere Claude does. But Cowork is home base.
Your folder. Your files. The workspace where you plan, build, run, and later edit your Skills. The home for the work.
Built once in Cowork (using the skill-creator), installed via Customize → Skills, then available everywhere — chat, projects, and Cowork itself.
Answer these in your chat with Claude. If you can't answer them, you're not ready to build yet — and that's a good thing to know.
Skills load every time they run. The more you stuff in, the more tokens they eat — and complex Skills can sometimes need real compute. The fix is the same as the design rule: keep them lean. One Skill, one job. Short, sharp, specific instructions. Don't try to make one Skill do everything.
Experts already have the ideas. They just need reshaping. The Nugget Finder turns your messy transcripts — workshops, calls, voice memos, podcasts — into a library of reusable IP. Quotes. Stories. Insights. The good stuff that usually disappears.
Open Claude. Follow along. We'll plan it in chat first, then wrap it as a Skill. Bring a real transcript — workshop recording, podcast, coaching call, even a long voice memo. If you don't have one, partner up.
Copy this shape into your Plan Mode chat. This is what we're building.
Raise your hand if you get stuck. We do not move on until everyone is on the same step.
Pre-flight check (60 seconds): Settings → Capabilities → make sure Code execution and file creation is toggled ON. Skills won't run without it. If it's already on, you're set.
The same Cowork you set up last workshop. Select your folder. Make sure you're on Opus + Extended thinking.
Home baseTwo ways to invoke it — pick whichever feels natural:
Option A — slash command: Type /skill-creator and follow the prompts.
Option B — natural language: Paste this:
The skill-creator asks the questions for you — categories, output format, how to handle long transcripts, what to ignore. Be specific. This is where the Skill gets its quality.
💡 If a question feels confusing, just say use a sensible default and move on. You can refine later.
Cowork creates the SKILL.md, runs an evaluation, and saves it straight into your Skills folder. No manual upload needed — Cowork picks it up automatically.
⚠️ Watch for an "Always allow" permission popup — click it so the eval can run. This is normal.
No upload requiredIn a new Cowork message, type exactly this and paste your transcript after:
Use the Nugget Finder skill on this transcript: [paste transcript here]
Watch your own gold come back. Stories you forgot you told. Phrases you didn't know were quotable.
You're live 🎉The magic moment: your own words come back as a usable IP library. Stories you forgot you told. Phrases you didn't know were quotable. The stuff that used to disappear.
A Skill isn't done when you ship it. It's done when it stops needing your attention. Until then, treat it like a living thing.
Use it. When something's off, open the Skill back in Cowork and add one specific rule. "Never use em-dashes." "Always end with a question." Tiny fixes compound — and Cowork makes editing easy once you're comfy.
Add a note in the Skill: "v1: original. v2: added emotion tags. v3: stripped corporate phrases." Future you will thank present you.
If you haven't used a Skill in a month, archive it. A small library of Skills you actually use beats a graveyard of Skills you don't.
Not three. Not a roadmap. The one Skill you'll build before next workshop. Use the planning questions. Plan it in chat first.
Each prompt below is ready to paste into Cowork. Same flow as the Nugget Finder — invoke the skill-creator, paste the prompt, answer the interview, save. Five new Skills, one per week, and you've got a system by month's end.
Turn robotic AI writing into something that actually sounds like you. The catch: it only works if you have a tone & voice guide to attach. Build that first.
⚠️ Prereq: a tone & voice guide doc in your Cowork folder. Without it, the Skill has nothing to reference.
Generate stronger first lines that earn the scroll-stop. Hooks live or die in the first 8 words — this Skill does the heavy lifting.
🔧 Still work-in-progress — the hook frameworks need tightening. Build it as v1, then refine using your best-performing posts as training data.
Turn a messy transcript or scrappy notes into a clean summary, action list, and deadlines. The Skill that pays for itself within a week.
💡 Pairs well with the Nugget Finder — run them in sequence on the same transcript for actions and insights.
Draft replies in your voice and tone. Not auto-send — draft, review, send. The hours back per week add up fast.
⚠️ Prereq: same tone & voice guide as Skill 01. Build that doc once — it powers multiple Skills.
Generate a proposal or contract draft from a discovery call, prefill the signer fields, and prep it for an e-sign service. The dream Skill for service businesses.
🚀 Stretch flag: the e-sign integration step (Adobe Sign, DocuSign, Dropbox Sign) needs API setup — that's a Skills 201 build. Start with v1 that just generates and prefills the doc. Send for signature manually until you're ready to wire up the API.
Skills are one tool. TTV is the whole system — PACE, AI toolkit, community, ongoing builds.
Join TTV membership