{"version":"2.1.317","anchor":"skill-sync-distinguishes-local-disk-failures-and-displaces-e","canonical_anchor":"skill-sync-distinguishes-local-disk-failures-and-displaces-e","heading":"Skill sync keeps an existing skill safe when an update fails","tier":"notice","area":"Skills","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/skill-sync-distinguishes-local-disk-failures-and-displaces-e","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Skill sync keeps an existing skill safe when an update fails\n\nSkill sync now moves an existing skill aside instead of deleting it, puts it back if the update fails, and reports local disk errors separately\n\n**What**\n\nSkills are add-ons that give Claude Code extra instructions or abilities, and they can be synced from an archive onto your computer. Two things changed in that sync.\n\nWhen a skill is being put in place and something already sits at that spot, Claude Code now moves the existing item aside instead of deleting it. If putting the new skill in place fails, the old one is restored. Before, a failed update removed the target folder and returned a general error.\n\nFailures caused by your own machine are now reported as a local problem, with a reason and the step where it happened. These include:\n\n- The disk being full (`ENOSPC`)\n\n- A disk quota being exceeded (`EDQUOT`)\n\n- A disk read or write error (`EIO`)\n\n- A read-only file system (`EROFS`)\n\n- Permission being denied (`EACCES`, `EPERM`)\n\n**Why**\n\nAn installed skill is less likely to be lost when an update goes wrong, and a failure caused by your disk or permissions is easier to tell apart from other sync problems.\n\n- Area: Skills\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}