<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Agent-Skills on Kevin Quinn</title><link>https://kevinquinn.fun/tags/agent-skills/</link><description>Recent content in Agent-Skills on Kevin Quinn</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Tue, 21 Apr 2026 05:00:00 +0000</lastBuildDate><atom:link href="https://kevinquinn.fun/tags/agent-skills/feed.xml" rel="self" type="application/rss+xml"/><item><title>My approach to Agent Skills: Occam's Razor</title><link>https://kevinquinn.fun/blog/my-approach-to-agent-skills/</link><pubDate>Tue, 21 Apr 2026 05:00:00 +0000</pubDate><guid>https://kevinquinn.fun/blog/my-approach-to-agent-skills/</guid><description>&lt;p>My current approach to Agent Skills is to not include them unless I feel the pain without them. The majority of the time I&amp;rsquo;m running 1-3 instances of vanilla Claude Code.&lt;/p>
&lt;p>To be clear, I&amp;rsquo;m not against Skills usage. I pull in Skills that have clear value, like helping agents use specific tools more effectively &lt;em>(e.g. &lt;code>playwright-cli&lt;/code> Skill)&lt;/em>. My only hold up with AI Augments&lt;sup id="fnref:1">&lt;a href="#fn:1" class="footnote-ref" role="doc-noteref">1&lt;/a>&lt;/sup> is that so few provide proof that they are better than using vanilla Claude Code.&lt;/p>
&lt;h2 id="every-skill-looks-the-same-on-paper">Every Skill looks the same on paper&lt;/h2>
&lt;p>So far I&amp;rsquo;ve found many Skills to be a lot of hype, but not a lot to back up their claims. Without clear measures, how am I supposed to distinguish between your amazing Skill you put a ton of effort into refining, and one that ostensibly does the same thing, but was one-shot prompted by a 12-year-old trying to promote their YouTube channel?&lt;/p>
&lt;p>To be fair, many Skills help with activities which are genuinely hard to measure. But it feels like if they had &lt;em>anything at all&lt;/em> to show they&amp;rsquo;re better than other Skills (or vanilla Claude Code), they&amp;rsquo;d be screaming it from the rooftops and you wouldn&amp;rsquo;t be able to miss it. As it stands, even for a popular suite of skills like &lt;a href="https://github.com/obra/superpowers/"
title="Superpowers: &amp;ldquo;An agentic skills framework &amp;amp; software development methodology that works&amp;rdquo;"
target="_blank" rel="nofollow noopener">
Superpowers: &amp;ldquo;An agentic skills framework &amp;amp; software development methodology that works&amp;rdquo;&lt;/a>
I struggle to find any concrete measures of WHY it&amp;rsquo;s better than plain vanilla tools. Ditto for basically every other Skill i&amp;rsquo;ve considered pulling in. If we can&amp;rsquo;t actually measure a Skill&amp;rsquo;s quality, are we just fooling ourselves by tweaking the tokens we use to arrive at the same place?&lt;/p>
&lt;p>It feels a bit like we&amp;rsquo;re following the PKM trend, where people build up incredibly complex Obsidian/Notion workspaces to make them more productive, and at the end of it&amp;hellip; they have a lot of artifacts of work, but not a lot of outcomes.&lt;/p>
&lt;h2 id="long-term-hypothesis-vanilla-wins">Long-term hypothesis: vanilla wins&lt;/h2>
&lt;p>I also subscribe to the hypothesis that the best Skills will eventually be eaten by the agent coding tools &lt;em>(like Claude Code)&lt;/em>, so I&amp;rsquo;ll end up getting the useful ones anyway. I could be wrong, but I believe we&amp;rsquo;ve already seen this happen with Claude Code with features like auto-memory, code execution, file tools like XLSX/PDF, scheduling routines, cloud agent runs, browser automation, as well as &lt;a href="https://platform.claude.com/docs/en/agents-and-tools/agent-skills/overview#pre-built-agent-skills"
title="pre-built Skills"
target="_blank" rel="nofollow noopener">
pre-built Skills&lt;/a>
which are bundled in without a user having to add them.&lt;/p>
&lt;p>It&amp;rsquo;s such a great vetting ground for the teams at Anthropic, OpenAI, etc. to watch which ones are rising to the top in popularity and then figure out how to bake them into the core product. Easier to acquire someone else&amp;rsquo;s innovation than have all the ideas yourself.&lt;/p>
&lt;hr>
&lt;div class="footnotes" role="doc-endnotes">
&lt;hr>
&lt;ol>
&lt;li id="fn:1">
&lt;p>Skills, commands, whatever the next hotness is.&amp;#160;&lt;a href="#fnref:1" class="footnote-backref" role="doc-backlink">&amp;#x21a9;&amp;#xfe0e;&lt;/a>&lt;/p>
&lt;/li>
&lt;/ol>
&lt;/div></description></item></channel></rss>