{"version":"2.1.234","anchor":"clearer-guidance-on-what-saving-a-skill-means","canonical_anchor":"clearer-guidance-on-what-saving-a-skill-means","heading":"Clearer guidance on what saving a skill means","tier":"notice","area":"Skills","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234\/e\/clearer-guidance-on-what-saving-a-skill-means","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234","markdown":"### Clearer guidance on what saving a skill means\n\nClaude is told that skill files on disk are a read-only cache, so editing them won't change your saved skill.\n\n**What**\n\nClaude is now told explicitly that skill files on disk, including synced copies of your account skills, are a read-only cache and that editing them does not change the saved skill. Three variants of this guidance exist for different session shapes.\n\n**Details**\n\n- One variant points at a tool for creating or updating a skill directly, one says to propose the skill with a different tool, and one says to produce a `.skill` zip or a single `SKILL.md` and hand it over.\n- That last variant warns there is no signal about whether you saved the file, so Claude should report the skill as delivered and never as saved.\n- A separate fragment carves out plugin-owned skills, which are customizable through their plugin.\n- Which variant applies depends on the session type; the selection logic is not part of this change.\n\n**Evidence**\n\n`report the skill as delivered, never as saved`\n\n- Area: Skills\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}