{
  "id": 20488019,
  "title": "Spec Kit now stamps a version on every skill it generates. Here's why that matters",
  "url": "https://urgent.news/2026/11/17/spec-kit-now-stamps-a-version-on-every-skill-it-generates-heres-why",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-11-17T20:26:26.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/louis_esterhuizen_8aa8bb8/spec-kit-now-stamps-a-version-on-every-skill-it-generates-heres-why-that-matters-25oe"
  },
  "original_language": "en",
  "account": "Last week, I wrote about outdated agent skills. Once a SKILL.md is copied into your skills folder, nothing tracks it. Your agent continues using the old instructions without any errors. Recently, GitHub Spec Kit released a fix for its own versioning issue. Now, every skill it generates includes the version that produced it.\n\nCore skills carry the Spec Kit version, while extension and preset skills have their own component version. This information uses the metadata map already present in the Agent Skills specification, so no spec change was necessary. The version was initially recorded in .specify/integration.json, but upgrading Spec Kit doesn't modify the existing skills on your disk. Only a version written directly in the skill itself indicates what you are currently running.\n\nIf you use a Spec Kit skill that is older than the latest release, you (and tools like Claude or Codex) will see a message indicating that the skill is out of date. For example: [skill-check] The skill speckit-plan is out of date: installed 1.4.1, latest v1.4.2. To update the skill, you need to run `specify self upgrade`, followed by `specify integration upgrade claude`.\n\nThe second key to determining if an update is available is the source metadata. This tells tools like skill-check where the original skill is hosted. By comparing your copy with the upstream version via version, content, and commit history, skill-check can catch updates even if the author forgot to update the version number. If you publish skills, adding these two metadata lines allows your updates to reach users who have copied your skill. If you have copied a skill without these lines, you can add the source information to your copy.\n\nThe skill-check tool is free and open-source, using the Apache-2.0 license. It doesn't require a server or collect telemetry, and it never blocks or modifies skills. You can add it to your agent or installer using the provided commands. There is an ongoing discussion on the Agent Skills specification about recommending these two metadata keys for better version management.",
  "summary": "Last week I wrote about stale agent skills : once a SKILL.md is copied into your skills folder, nothing tracks it. Your agent keeps following the old instructions, and nothing errors out. Five days later, GitHub Spec Kit shipped a fix for its own corner of the problem. What changed Since Spec Kit 1.4.2, every skill it generates records the version that produced it: --- name : speckit-plan…",
  "key_points": [
    "Spec Kit now includes version in generated skills",
    "Version added to metadata map, no spec change needed",
    "Outdated skills flagged with update instructions"
  ],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}