Ben's Hermes agent: 100+ skills (after pruning)
Ben's Hermes personal agent had well over 100 skills even after he deleted about 50, illustrating how quickly skill files accumulate.
Where this was said
Claude Code Skills: Why AI-Generated Ones Fail
At 22:54 · 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.
How to Actually Build Good Skills: Mine Your History
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.
Similar snapshots
Ad monetization for games
Ad-based monetization works well for game apps where users spend extended time in-session, as seen with Grid and Wordle.
Ads don't work for tool apps
Tool-focused apps like PuffCount are poor candidates for ad monetization because users don't stay in-session long enough.
Hard paywall is unskippable
A hard paywall is a screen that blocks all app features unless the user pays or starts a free trial — it cannot be dismissed.
Two core monetization models
Mobile apps are primarily monetized through either ads (best for games) or in-app purchases/subscriptions (best for tools).
YouTube beats every other platform
According to the episode, YouTube outperforms every other social platform for building trust and driving SaaS conversions.
Most users came from YouTube
Vasco stated that the majority of his app's user base came directly from his YouTube channel.
Boost My Domain Rating button
SEO Bot features a 'Boost My Domain Rating' button that routes users directly to Listing Bot, an example of in-product cross-selling.
All products connected to AI
The founder's entire product portfolio is AI-related, making it easier to package products attractively for directories.
AI coding viability debate as hook
The founder attached their SaaS demo to the trending debate about whether AI coding is actually good enough to build a full SaaS product.
