{"version":"2.1.281","anchor":"synced-skill-cleanup-also-prunes-listedskills-bare-name-res","canonical_anchor":"synced-skill-cleanup-also-prunes-listedskills-bare-name-res","heading":"Skill sync tracks listed skills and new missing-skill resync state","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/synced-skill-cleanup-also-prunes-listedskills-bare-name-res","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Skill sync tracks listed skills and new missing-skill resync state\n\nSkill sync gains a listedSkills list and missing-skill resync fields, and changes when a synced skill claims its short name\n\n**Unclear.** The finding does not say what `listedSkills` holds or which skills gain or lose their short name under the new rule.\n\n**What**\n\nSkill sync is the part of Claude Code that keeps synced skills up to date. It now keeps more records about those skills, and it cleans up and resets them.\n\n- Cleanup of synced skills now removes stale entries from a new `listedSkills` list, as well as leftover placeholders.\n\n- Resetting skill sync now clears `listedSkills` and resets two new fields, `missingSkillResyncAt` and `missingSkillResync`. Before, a reset cleared only pending downloads and placeholders.\n\n- A synced skill can reserve its bare name, meaning its short name without a prefix. The rule for when it does this changed: it no longer just checks whether the skill's `aliases` include that short name, and a separate check now decides.\n\n**Why**\n\nThis is mostly internal bookkeeping with little you will see directly. The new field names point to a re-sync step for skills that are missing, but the members do not show what triggers it."}