{"version":"2.1.275","anchor":"skillmd-edits-tell-claude-which-tool-saves-the-change","canonical_anchor":"skillmd-edits-tell-claude-which-tool-saves-the-change","heading":"Warning when editing a SKILL.md file that won't actually save","tier":"notice","area":"Skills","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275\/e\/skillmd-edits-tell-claude-which-tool-saves-the-change","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275","markdown":"### Warning when editing a SKILL.md file that won't actually save\n\nEditing a skill file inside the synced-skills folder now warns Claude and the user that the change may not be saved\n\n**What**\n\nWhen Claude edits or writes a `SKILL.md` file, the Edit and Write tool results now include a `syncedSkillNext` field with guidance whenever that file sits in the folder that holds synced copies of the user's account skills. Edits made directly in that folder aren't actually saved and can be overwritten the next time skills sync, so the guidance tells Claude to instead use a save tool, call a propose tool, send the file to the user to save manually, or, if none of those are available, tell the user the change wasn't saved.\n\n**Why**\n\nThis stops silent data loss: without it, an edit to a synced skill file could look successful but disappear on the next sync.\n\n- Area: Skills\n- Names: `SKILL.md`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}