Every Skill has one moment that matters most.
You've been building Skills for yourself the whole way through Skills Workshop. That's what Sprouts and Makers were for. This module is different. This module is about the moment when you decide to put a Skill into the world — with your name on it — so somebody else can use it.
It's called shipping.
"Ship" means the thing stops being yours and becomes something other people can pick up. It's the moment a Skill stops being a note-to-self and starts being a gift.
Shipping is small. Shipping is also permanent. The first version you publish is the one people judge you on — not because it has to be perfect, but because it's the one with your name attached. This module is about doing it carefully without doing it slowly.
Everything else in Skills Workshop — specificity, composition, voice, memory, collaboration, testing, versioning, refusal — lives inside your own head. This is the one where you say the hardest sentence: "Here. You use it now. I made this."
Ask yourself three questions first.
Most first-time publishers skip these questions and end up either shipping something they regret or never shipping at all. The three questions sit in between those two mistakes — they help you decide carefully without paralyzing.
Is it actually good enough?
Not perfect — good enough. If you've run test cases (Module 01) and they pass, the answer is probably yes. If you haven't, the answer is "go write tests first." The floor is: would I be embarrassed if my favorite teacher saw this Skill? If no, it's probably good enough. If yes, one more pass.
Does it have something only I would have made?
This is the specificity test from Module 02, flipped around. Could a stranger on the internet have written a nearly-identical Skill? If yes, you're not adding anything to the world — you're just taking up space. The world already has enough generic Skills. Ship only what's unmistakably yours.
Am I comfortable with my name on it forever?
Shipping is permanent. Ten years from now, someone might find this Skill and know you made it when you were 14. Would that bother you? If no, ship it. If yes, find the thing that bothers you and either fix it or don't ship yet. Pride and regret are both useful — listen to them.
If all three answers are yes, ship today. If any answer is no, the thing to fix is obvious — go fix that one thing and come back. Don't treat this like a big decision. Treat it like a checklist.
Three things you must declare.
Shipping isn't just uploading a file. It's declaring three specific things — three answers other people need in order to use your Skill responsibly. Miss any of them and you're shipping something half-broken.
Attribution
Who made it? Just your first name is fine. Add your age if you want — a lot of kids are proud to say "I made this when I was 12." Don't hide it, don't fake it.
Provenance
Where did this knowledge come from? If you interviewed your grandma (Module 03), say so. If you learned from a friend, say so. Provenance is the chain of people behind your Skill.
License
How can other people use it? The simplest answer is CC0 (use it any way you want, no strings). But sometimes you'll want attribution required. Pick one and be clear.
All three of these fit in about ten lines of YAML. You don't need a lawyer or a university. You need the same honesty you've been practicing the whole way through Skills Workshop — just pointed outward, at the world, instead of inward.
A published Skill is three files, not one.
The Skill itself is only the middle file. A proper publication adds two siblings: a metadata file that answers the three declarations, and a readme file that tells a stranger what the Skill is for.
The declarations
Attribution, provenance, license, version — the facts a publishing system needs.
The actual Skill
The file you've been making this whole time. No changes needed — it's the star of the show.
The introduction
One page of human writing that tells a stranger what the Skill does, why it exists, and how to use it.
Here's what a real metadata file looks like. This is everything a publishing system needs to track your Skill responsibly.
# Publishing metadata for my-dog-buddy # Everything a stranger needs to use this Skill responsibly skill_file: "buddy.skill.yaml" version: "2.1.0" published: "2026-04-02" # === ATTRIBUTION === author: name: "Maya" age_when_made: "12" contact: "through my parents, ask at Kindling showcase" # === PROVENANCE === provenance: - "Facts about Buddy observed by me over 2 years" - "Treat fact confirmed with my mom (she buys them)" - "Scar origin story from my dad's memory" # === LICENSE === license: CC-BY-4.0 license_plain: "You can use this Skill freely — I just ask that you keep my name in the attribution." # === SCOPE (from Module 03) === safe_to_use_for: - "Learning about a specific dog" - "Writing stories that include Buddy" not_meant_for: - "Medical / veterinary questions" - "Dog training advice in general"
And here's the readme that goes with it. It's the most human part of the bundle — no YAML, just one page of real writing.
# My Dog Buddy — a Skill by Maya, age 12 This is a Skill about my dog Buddy. He's a 3-year-old golden retriever who lives with me and my family in a house on Oak Street. I made this Skill so Claude could write stories and answer questions about him the way I would — not the way a generic golden retriever article would. ## What it's good for - Writing stories or comics where Buddy appears - Getting Claude to talk about him like someone who knows him - Reminding me of details about him I might forget ## What it's NOT good for - Medical or vet questions (ask my parents, not this Skill) - Training advice for other dogs (Buddy is weird, he's not a template) ## Why I made this Because when I asked Claude about Buddy the first time, it said "golden retrievers are friendly and love fetching balls" and I got mad. Buddy is a specific dog. He deserves a specific Skill. ## Want to use it? Go ahead. License is CC-BY, which means you can do anything with it except remove my name from the attribution. If you use it somewhere cool, I'd love to hear about it (ask at the Kindling showcase). — Maya
Write your own publishing metadata.
Pick any Skill you've made in Skills Workshop. Fill in the form. The metadata builds itself as you type.
# Fill in the form above and watch this update. skill_file: ... author: ... license: ...
This is the hardest-looking builder in Skills Workshop, but it's the shortest in terms of real work. Most fields are one line. The point is the deciding, not the typing.
Not every Skill should be published.
The constraints from Module 03 are about what a Skill refuses to answer. This is about what a person refuses to publish. Two rounds of judgment.
Round 1. A kid has a Skill about their best friend Theo — his personality, his jokes, his favorite things, stuff only they know. Should it be published?
Round 2. A kid made a Skill about their grandma's dumpling recipe (from Module 03). Grandma said "sure" when asked. Should it be published?
If a Skill contains knowledge from another person, publishing it requires their permission, not just yours. The smaller the circle of people involved, the more important the ask becomes. This is where empathy from Sprouts Module 03 grows up into real ethics.
You just finished Skills Workshop.
All eleven modules. Every level. Every pattern. You've gone from writing one sentence about your dog to publishing a real artifact into the world.
Everything you learned across all eleven modules
Skills Workshop started out as a way to teach Claude what only you know. By the end, it became something bigger — a way of thinking about your own knowledge carefully enough to share it with other people. That's not a computer skill. That's a life skill. The computer was just the excuse.
From here, you have three places to go:
★ Before you call it done
Three questions. Same three. Every time.
These are the same three questions for every module in Kindling. They are how you check whether AI did the part it should and you did the part only you could. Tap each one to mark it true.
★ ★ ★