Quick Overview
The 1935 crash that invented the checklist: How aviation solved a problem that looks exactly like the one you have with Claude.
What Skills actually are: The folder Claude reads when it's relevant, and ignores when it's not.
Projects vs Skills: Constant context vs on demand expertise, and why most people only build one.
Three Skills worth building this week: Brand voice, research, and email patterns.
The compound effect: Why Memory, Projects, and Skills together are the real moat.
In 1935, the US Army Air Corps watched its newest bomber crash on takeoff. ✈️
The pilot was Major Ployer Hill, one of the best in the corps. The plane was the Boeing Model 299, soon to become the B-17. Investigators found nothing wrong with the aircraft. The verdict was almost embarrassing for an institution built on training. The plane was "too much airplane for one man to fly."
The fix nobody respected at the time wasn't more flight hours. It wasn't a smarter pilot. It was a checklist.
A printed list of every step before takeoff, during flight, and on landing. The B-17 went on to fly 1.8 million combat hours. Every cockpit since has carried one. The unlock wasn't intelligence. It was a system.
Most people use Claude like that pilot.
Brilliant tool. Zero system. They re-explain their voice every chat, paste the same brief into 14 conversations a week, and when the output drifts they blame the model. The model isn't the problem. The cockpit is.
What Skills actually are
A Skill is a folder. Inside it sits a markdown file with three things. A name, a description, and instructions Claude reads when your request matches the description.
That's the entire trick.
Claude scans the descriptions of all your active Skills in the background. When something fits what you're asking, the full instructions load. When nothing fits, they stay dormant. You don't summon Skills. They summon themselves.
Projects vs Skills
A Project loads its knowledge into every chat in that workspace. A Skill loads its instructions only when the task calls for them.
Projects = constant context. Skills = on demand expertise.
You want both. A Project anchors what Claude needs to know about your business at all times. Skills inject specialist instructions only when the task triggers them, so simple chats stay light and complex ones get the heavy artillery.
Three Skills worth building this week
Brand voice Skill. Your hook formulas, sentence rhythm rules, words you never use, sign-off patterns. Triggers any time you ask Claude to draft content.
Research summary Skill. How sources should be weighed, what counts as a credible claim, when to flag uncertainty, what never to paraphrase. Triggers when you ask for analysis or breakdowns.
Email pattern Skill. Your subject line logic, your opening hook structures, your CTA rules. Triggers any time you say "write an email."
Each one takes a single sitting to write. Each one saves you that same sitting every time you use Claude afterward.
The compound effect
The real moat isn't any single feature. It's the stack.
Memory remembers facts about you across chats. Projects load persistent context for a workspace. Skills inject expertise when the task calls for it. Most operators build none of these. The few who build all three move at a different speed, not because they're smarter, but because they've stopped solving the same problem twice.
The verdict
The B-17 never got smarter. The pilots got a system. Same logic here. The model isn't the leverage. The cockpit around it is.
Stay sharp.