Where this was said
Claude Code Skills: Why AI-Generated Ones Fail
At 16:28 · chapter starts 14:20
Matt Pocock's missed AIE talk — posted online instead — becomes the launching pad for one of the episode's most technically dense segments. His core argument: don't let AI write your Claude Code skills. The reason is elegant and non-obvious. [1] — Theo "The fundamental problem with letting AI write your Claude Code skills is that models write what they already do by default. Skills are supp…" 14:00 The entire purpose of a skill is to give the model behavior it doesn't have by default. When the AI writes the skill itself, it naturally gravitates toward behaviors it already exhibits, creating elaborate no-ops stuffed with filler like 'be really thorough' — instructions the model would follow anyway. Ben admits he's guilty of this pattern himself. The right workflow, Theo argues, is to go through your full model usage history, find every time you had to correct the model, categorize those failures, and write skills that specifically redirect the model away from those documented failures. Both hosts then open their .clod directories live and compare skill counts — Ben has 8 in his global directory and over 100 in his Hermes agent (after pruning 50), while Theo has trimmed aggressively to just a handful. The discussion covers workflow skills, framework-specific skills (Svelte, Effect), and the important distinction between things that belong in Agents.md versus a full skill.
The best skills come from analyzing your full usage history, finding repeated correction patterns, and writing guidance that steers the model away from documented failures. Writing a skill once and never revisiting it is almost always wrong — treat skills like living documents.
Ben's Hermes personal agent had well over 100 skills even after he deleted about 50, illustrating how quickly skill files accumulate.
