How to make really good Claude skills (clearly explained in 42 seconds)
The transcript outlines a method for creating high-quality Claude skills by providing context, defining clear criteria, iterating until successful, and letting the AI write the skill itself. The process emphasizes testing and collaborative debugging to ensure reliability. The speaker argues AI-written skills outperform human-written ones because they reflect what actually worked.
Summary
The speaker addresses a common problem with Claude skills: average output quality resulting from a lack of personalized context. The solution begins with grounding the skill in specific, real-world criteria. Using a lead research agent as an example, the speaker suggests instructing the AI to check sources like Twitter, YouTube, and Trustpilot, and to reject leads immediately if two or more sources are missing or unfavorable. This clarity of definition sets up the next phase effectively.
The second major phase is iteration. The speaker recommends running the process multiple times until a clean, end-to-end run is achieved. Once that happens, the key insight is to have the AI itself review what it just did and convert that successful run into a formalized skill. The speaker's argument is that the AI will write a better skill than a human would, precisely because it has firsthand knowledge of what actually worked during the iterations.
Finally, the speaker emphasizes rigorous testing. If the skill breaks, the recommendation is to ask the AI why it failed, fix the issue collaboratively, and test again. This iterative debugging loop is framed as essential to ensuring the skill remains robust and does not break in the future. The overall framework is: contextualize, iterate, let AI formalize, and test collaboratively.
Key Insights
- The speaker argues that Claude skills produce average output by default because they lack the context of the user's specific style and criteria.
- The speaker uses a lead research agent example, specifying that checking Twitter, YouTube, and Trustpilot — and rejecting leads if two are missing or poor — is how you define acceptable standards within a skill.
- The speaker claims that running multiple iterations until a clean end-to-end run is achieved is a necessary step before formalizing any skill.
- The speaker argues that having the AI review its own successful run and write the skill from that experience produces better results than a human writing the skill manually.
- The speaker frames collaborative debugging — asking the AI why something broke, fixing it together, and retesting — as the critical step to ensuring a skill never breaks again.
Topics
Transcript
[0:00] Every time you create a claude skills, the output is often average. That's because skills lack the context of your style. Say you're building a lead research agent. Tell it to check their Twitter, YouTube, and Trust Pilot. If two are missing or look bad, reject instantly by defining what's okay and what's not. You set it up for the next step, iteration. Run multiple iterations until you get one clean run end to end. Then ask the AI to review what it just did and turn that into a skill. AI writes a skill better than you will [0:30] because it now knows what actually worked. Finally, test the skill. If something breaks, ask it why. Fix it…
Full transcript available for MurmurCast members
Sign Up to AccessMore from Greg Isenberg
What are Agentic Loops?
Professor Ross Mike explains agentic loops — AI systems that self-iterate without human input — and argues they are largely impractical for most developers due to high token costs and poor assumption-making. He distinguishes between 'human in the loop' (iterative, guided development) and fully automated loops, recommending loops only for constrained, binary-feedback processes like code review. He shares his own GP loop use case as a rare valid example.
Clearest Explanation of AI Agents as Customers
The speaker argues that AI agents are becoming the primary 'customers' of the internet, replacing human users as the dominant force driving web traffic and commerce. This shift requires entirely new infrastructure — from agent-native inboxes and wallets to machine-readable websites — creating massive startup opportunities. The speaker frames this as a bifurcation of the internet into a human layer and an agent layer.
How to use Obsidian with Claude in 61 seconds
This short tutorial outlines three levels of using Obsidian with Claude AI to accelerate professional learning and career resilience. It covers connecting Obsidian to Claude via MCP, using the Smart Connections plugin to identify skill gaps, and prompting Claude to generate a public learning plan based on your notes.
Been playing with this cool ai tool from genspark
The video demonstrates how GenSpark's AI tool can automate LinkedIn job post lead generation by identifying decision makers and drafting personalized cold emails. It then presents a business model called 'Outcome as a Service,' where users build competitor-tracking workflows and sell daily briefings to clients for recurring revenue.
Hermes Agent Explained
The transcript introduces Hermes, an AI agent that retains memory across sessions unlike standard LLMs. It highlights key features including cost-efficient reasoning via Open Router with Quen 3.6 Plus, Obsidian integration for persistent context, and cron job automation for token-free repetitive tasks. The entire stack is noted to run on an Android phone.