---
slug: /guides/claude-skill-update-old-files/
title: "Claude skill updated, but still using old files? Check these three layers"
description: "Compare the listed skill, the files your runtime actually loads, and its supporting references. A practical skill-update diagnostic for agent builders."
date: 2026-11-13
product: skill-change-control-desk
---

# Claude skill updated, but still using old files?

Check three things separately: **the description you see, the files the runtime loads, and the supporting files those instructions require.** An updated description alone doesn't establish that the installed skill changed.

For developers managing several skills or runtime profiles, this distinction turns a vague “the agent ignored my update” problem into a concrete review.

## 1. Identify the copy your agent is using

Record the runtime, version and active profile. Ask the agent to identify the skill's loaded location using the tools that runtime provides. Compare it with the location you intended to update. Preserve a copy before changing anything.

Then inspect one distinctive change from the new release: a new helper, a renamed reference or a revised instruction. Check the actual file, not just a description in a picker.

A [Claude Code issue opened October 21](https://github.com/anthropics/claude-code/issues/104021) reports exactly this mismatch on Windows: a skill's description changed while its local files remained old. That is a user-reported case, not a diagnosis of every installation. Its useful lesson is to verify the installed contents independently of the listing.

## 2. Follow the supporting-file paths

A skill is more than its SKILL.md. If its instructions refer to a glossary, script or template, check that the file exists where the loaded copy expects it.

Work through one reference from beginning to end:

- Which file contains the reference?
- What path does it name?
- Does that path resolve from the installed location?
- Does the resolved file belong to the intended release?

An [October 19 desktop issue](https://github.com/anthropics/claude-code/issues/103509) describes skills loading without shared plugin-level reference files, although the reporter's Claude Code installation could resolve them. The practical takeaway: verify the installed layout in each target runtime rather than assuming the source repository's layout was preserved.

## 3. Separate an update from a local customization

Compare the previous release, the candidate release and your installed copy. A difference may be a deliberate team override rather than something to erase.

Use a small review record:

| Check | Record |
| --- | --- |
| Intended source | Release, commit or downloaded archive |
| Active installation | Runtime, profile and loaded path |
| Expected change | File or behavior that should differ |
| Actual change | Observed file difference or missing dependency |
| Local override | Customization to preserve or intentionally replace |
| Next step | Scoped update, dependency repair or upstream investigation |

Keep the review scoped to the affected profile. Verify a representative task after the change and retain the previous copy until the result is right.

## Turn repeated update reviews into a reusable workflow

**Skill Change Control Desk** packages four coordinated skills for intake, update review, scoped rollout planning and drift triage. Its local Python tools produce inventory, diff and plan reports from supplied files. Worked examples help your agent turn those records into a clear update recommendation.

Use it when you manage multiple skill sources, local customizations or runtime profiles and want a repeatable review instead of starting from scratch each time. Installation stays with your existing package manager; the Desk provides the review workflow and local tools.

**[Buy the four-skill pack · $12](/skill-change/checkout/)**

One-time download, plus applicable tax. Python 3.10+ for the local tools. Commercial use included. [See the contents and purchase terms](/shop/skill-change-control-desk/).