You already do the hard part.
Every time you correct Claude about something studio-specific — a build flag that changed, a naming rule it didn't know, a crash signature you finally tracked down — you've already done the diagnostic work. The only thing missing is writing it down somewhere the next person's Claude can read it. That's a skill update. That's this page.
Shorter than it looks.
A skill is one markdown file living in the repo — .claude/skills/<name>/SKILL.md. A short header telling Claude when to reach for it, then a body written exactly like you'd brief a sharp new hire.
That's the whole shape. Longer skills add more sections (conventions, known-issues tables, checklists) — but the header + what-it-does + our-commands + try-it skeleton above covers 90% of what you'll ever write.
From "that was annoying" to "fixed for everyone."
Notice the friction
Claude guessed wrong, used an outdated flag, or you explained the same convention twice. That's your signal — don't let it pass as "eh, I'll just remember for next time."
Ask Claude to make the edit
You don't need to hand-write markdown. Tell Claude what changed and where the skill lives; it drafts the diff.
Sanity-check the diff
Read what changed. Does it match what you'd tell a new hire? If Claude's phrasing is off, say so — this is a normal review, not a rubber stamp.
Test it in a fresh session
Ask a brand-new Claude session (no memory of your conversation) to do the task the old way, and confirm it now follows the update. Cheap insurance against a typo silently breaking the skill.
Open the PR, say one sentence
Normal review, normal merge. Drop one line in the team channel — "updated build-and-cook, the old -stage flag is gone" — so people don't waste time rediscovering what you just fixed.
"Open a PR" means one specific place.
Our skills aren't scattered across laptops — they live in one versioned library that every machine installs from and refreshes automatically, so a skill you sharpen on Tuesday is in everyone's Claude by Wednesday without a single message in a channel. That's the whole reason ten minutes of your time is worth spending here. If you're curious how the distribution works — or you're the person who has to set it up — it's on Studio Setup.
A real example, start to finish.
Claude guesses, and guesses wrong
Someone asks Claude to cook a build. It reaches for a cook flag that worked six months ago. The cook fails. Twenty minutes disappear figuring out why, again — the same twenty minutes someone else already spent last month.
One correction, permanent fix
Same failure — but this time, the person hitting it says "update the skill" instead of just fixing their own build. Five minutes later, a PR lands. Every future cook, from anyone's Claude, uses the right flag from the first try.
The difference between those two futures isn't skill — it's whether the fix got written down. That's the entire pitch for this page.
Don't have five minutes? Thirty seconds works too.
No PR, no markdown, no ceremony. Tell us what's missing or what's wrong, and whoever owns the library will turn it into a skill update.
Got it — thank you.
This lands with whoever triages the skill library. If it's straightforward, expect it folded into a skill within a few days. If we need more from you, we'll follow up.