The first academy. Two projects: in the first you write a Claude Skill from scratch. In the second you make it actually work — for someone in your life who actually uses it.
Anyone can prompt Claude to "write a quiz." That's the median Skill — and the result is forgettable. Skills Workshop is the opposite move: you teach Claude what only you know, in your specific words, with your specific examples.
By project two you've shipped a Skill that someone — your sibling, your cousin, your friend — actually installs and uses. With a "what I don't help with" rule. With at least one fix you made because a real person got confused.
It is not a tutorial on prompt tricks. It is not "make Claude do your homework." It is not a place to make a generic "fitness coach" or "study buddy" Skill — those already exist, and yours wouldn't be any better.
The whole academy refuses to let you build something that isn't specific, yours, and useful to a person whose name you know. If you can't name the person, you go back a step.
Pick a domain you actually know more about than your friends — Minecraft redstone, basketball plays, k-pop lore, dog breeds, anything. Write a Skill that thinks the way you do about it.
You ship → SKILL.md + 3 example outputs that prove the Skill knows what only you would teach.
Show your Skill to 3 friends. Watch them use it without helping. Note what confuses them. Make 3 fixes. Add a "what I don't help with" section so the Skill politely says no when it's out of its depth.
You ship → SKILL.md v2 + 3 friends' notes + 3 documented fixes + 1 "I don't help with" rule.
A Claude Skill that someone in your life actually uses. Three real fixes you made because of real feedback. The understanding that a Skill saying "I don't help with that" is sometimes the most useful thing it can say. That's a real engineering instinct. Carry it forward.