You hire someone, hand them a client presentation, tell them they are not allowed to ask a single question, and promise to fire them if the first draft is bad. Nobody runs a team that way, yet it is roughly how a lot of us hand work to Claude and ChatGPT, then forward whatever comes back to a customer. This one is for anyone whose company is starting to drown in AI output nobody checked, and for the leaders tempted to ban the tool because of it.

The problem starts before the prompt. Most knowledge work is tacit: you know how to do it until you have to explain it, which is the illusion of explanatory depth, so the ask stays vague and the model fills the gap. Chris shows what that looks like with one plain Opus 5.5 prompt for the Said and Unsaid newsletter, which came back with placeholders and a guessed format, then walks through /saidandunsaid, an orchestrator skill with no logic of its own. It calls research, outline, draft, a fresh-subagent cold read, image and render subskills, and a human picks the story at the start and reads the draft at the end.

Then it moves into the enterprise: where organizational skills live in Claude under Customize, why a skill your company already published beats one you build yourself, and why banning AI after a bad draft pushes the work into shadow AI, which IBM's 2026 breach report ties to 43% of breaches. Sash adds the recipe-book view: you never have to write a skill file by hand. Have Claude interview you with the skill creator, or take a plugin someone else built and customize it.

Key takeaways:

• Make your AI ask you questions before it builds anything - say so in the prompt, or use a brainstorming or grill-me style skill that does it for you.
• Turn any task you repeat into a skill: the instructions, the rules, and two or three examples of output you consider good.
• Keep the orchestrator free of logic: one top-level skill that only calls subskills, so you can change or reuse one step without breaking the rest.
• Before you build a skill at work, open Customize, then Skills, and check the Organization section - a team may already have built it.
• Don't ban AI after one bad draft. Make a named person accountable for what ships, and give them skills that make good output the default.

Watch the video version on YouTube · Full show notes, transcript + takeaways