{"version":"1.0","type":"rich","provider_name":"Acast","provider_url":"https://acast.com","height":250,"width":700,"html":"<iframe src=\"https://embed.acast.com/$/69ab3b7c7036d739021982df/6a6e39ed61ae402f619cc9e6?\" frameBorder=\"0\" width=\"700\" height=\"250\"></iframe>","title":"Agent Skills: How to Test One Before You Keep It","description":"<p>Your AI tools already ship with skills—but installing more of them can quietly make the results worse.</p><p>Nate explains what a skill actually is, why skills are instructions rather than apps, and why the real audience for a skill is the agent using it. He breaks down SKILL.md, loading order, front matter, vague triggers, conflicting instructions, security boundaries, and the difference between collecting skills and deliberately shaping them for your own workflow.</p><p><br></p><p>The episode moves from a beginner-friendly definition to the advanced problem of auditing a stack of 20–25 skills. The practical takeaway: use existing skills as raw material, then sharpen them around the work, preferences, and principles that are uniquely yours.</p><p>Topics include:</p><p><br></p><ul><li>Skills as recipes for AI agents</li><li>Why skills are not apps</li><li>Agents as the audience and humans as readers</li><li>Name, description, front matter, and loading order</li><li>Security, permissions, and trust</li><li>The Pokémon-card trap of collecting skills</li><li>Conflicts across a large skill stack</li><li>Building and auditing skills for your own workflow</li></ul><p><br></p>","author_name":"Nate B. Jones"}