<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Louis Esterhuizen</title>
    <description>The latest articles on DEV Community by Louis Esterhuizen (@louis_esterhuizen_8aa8bb8).</description>
    <link>https://dev.to/louis_esterhuizen_8aa8bb8</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F1506690%2Fd0dce7ae-4890-421f-b154-564769dd90ff.jpg</url>
      <title>DEV Community: Louis Esterhuizen</title>
      <link>https://dev.to/louis_esterhuizen_8aa8bb8</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/louis_esterhuizen_8aa8bb8"/>
    <language>en</language>
    <item>
      <title>Your agent is probably running stale skills</title>
      <dc:creator>Louis Esterhuizen</dc:creator>
      <pubDate>Fri, 13 Nov 2026 23:20:55 +0000</pubDate>
      <link>https://dev.to/louis_esterhuizen_8aa8bb8/your-agent-is-probably-running-stale-skills-18pe</link>
      <guid>https://dev.to/louis_esterhuizen_8aa8bb8/your-agent-is-probably-running-stale-skills-18pe</guid>
      <description>&lt;p&gt;Agent skills are folders with a &lt;code&gt;SKILL.md&lt;/code&gt; that teach Claude Code, Codex and other agents how to do something specific: review a React app, plan a feature with Spec Kit, write a Hugging Face training script. They're easy to share, so most people install them the simple way, by copying the folder into their skills directory.&lt;/p&gt;

&lt;p&gt;That's where it goes quietly wrong. Once a skill is copied, nothing tracks it. The author fixes a mistake, adapts to a new API, or rewrites the instructions, and your copy stays as it was. And a stale skill doesn't fail. There's no error, just an agent that follows last spring's advice and does slightly worse work, and you have no reason to suspect the skill.&lt;/p&gt;

&lt;h2&gt;
  
  
  How common is this?
&lt;/h2&gt;

&lt;p&gt;I counted the 597 &lt;code&gt;SKILL.md&lt;/code&gt; files in seven of the biggest public collections: Anthropic's, OpenAI's, GitHub's awesome-copilot, Hugging Face's, Vercel's, obra/superpowers, and the skills bundled with Codex.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Only 41 record a version at all (&lt;code&gt;metadata.version&lt;/code&gt;), and only 17 say where they came from (&lt;code&gt;metadata.source&lt;/code&gt;).&lt;/li&gt;
&lt;li&gt;Most of those versions are &lt;code&gt;"1.0"&lt;/code&gt; or &lt;code&gt;"1.0.0"&lt;/code&gt;, and they stay that way. Vercel's &lt;code&gt;react-best-practices&lt;/code&gt; has changed in more than ten commits since January and still says &lt;code&gt;1.0.0&lt;/code&gt;.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;So even when a skill has a version number, comparing version numbers would miss most updates. And 580 of the 597 carry no record of where they came from, so a copy of one can't find its way back.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I built
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://github.com/louis8408/skill-check" rel="noopener noreferrer"&gt;skill-check&lt;/a&gt; is a small open-source plugin for Claude Code and Codex. At the moment a skill is used, it checks whether a newer version exists and, if so, shows a warning:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;[skill-check] The skill "speckit-plan" is out of date: installed 0.12.0, latest v0.13.1.
Run `specify self upgrade`, then `specify integration upgrade claude` in this project.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The agent sees the warning too, mentions it to you, and carries on. Nothing is blocked.&lt;/p&gt;

&lt;p&gt;It knows a skill is stale in three ways:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;&lt;code&gt;metadata.source&lt;/code&gt; in the SKILL.md.&lt;/strong&gt; It compares your copy with the upstream copy at that URL: by version when upstream's is higher, otherwise by content and, for GitHub sources, the file's commit history. That's how it catches the &lt;code&gt;1.0.0&lt;/code&gt; skill that changed ten times: it matches your copy to the commit it came from and sees that upstream has moved on.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Spec Kit.&lt;/strong&gt; &lt;code&gt;speckit-*&lt;/code&gt; skills are compared with the latest Spec Kit release.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;&lt;code&gt;npx skills&lt;/code&gt;.&lt;/strong&gt; Skills installed with &lt;code&gt;npx skills add&lt;/code&gt; are compared with the hash in its lock file.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;A check runs in the background when a session starts, and results are cached for a day, so using a skill is instant. Offline or rate-limited means silence, never a broken session. It has no server and no telemetry, and it only fetches the public files it compares against.&lt;/p&gt;

&lt;h2&gt;
  
  
  The convention matters more than the tool
&lt;/h2&gt;

&lt;p&gt;The part I care about most is two lines any skill author can add today, with no changes to the Agent Skills spec:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight yaml"&gt;&lt;code&gt;&lt;span class="na"&gt;metadata&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
  &lt;span class="na"&gt;version&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mf"&gt;1.2.0&lt;/span&gt;
  &lt;span class="na"&gt;source&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;https://github.com/you/your-skills/tree/main/your-skill&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;code&gt;source&lt;/code&gt; is the important one: it travels with every copy, so any tool, not just mine, can find the upstream again. &lt;code&gt;version&lt;/code&gt; is a useful hint on top. I've written it up as a short convention (&lt;a href="https://github.com/louis8408/skill-check/blob/main/CONVENTION.md" rel="noopener noreferrer"&gt;CONVENTION.md&lt;/a&gt;, CC BY 4.0) and shared the evidence on the &lt;a href="https://github.com/agentskills/agentskills/discussions/564" rel="noopener noreferrer"&gt;Agent Skills spec discussion&lt;/a&gt; that proposes the same keys. If agents end up checking this natively, skill-check will have done its job.&lt;/p&gt;

&lt;h2&gt;
  
  
  Try it
&lt;/h2&gt;

&lt;p&gt;Claude Code:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;/plugin marketplace add louis8408/skill-check
/plugin install skill-check@skill-check
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Codex:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;codex plugin marketplace add louis8408/skill-check
codex plugin add skill-check@skill-check
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;You need Node.js 20 or later. The README has a two-minute "Try it" that installs an outdated example skill so you can see the warning, and a &lt;code&gt;check&lt;/code&gt; command that lists the status of every skill you have.&lt;/p&gt;

&lt;p&gt;If you maintain skills: please add &lt;code&gt;metadata.source&lt;/code&gt;. It's one line, and it's what lets your fixes reach the people who copied your skill.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;I built skill-check with Claude Code's help, and Claude Code helped draft this post.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>claude</category>
      <category>opensource</category>
      <category>productivity</category>
    </item>
  </channel>
</rss>
