{"version":"2.1.248","anchor":"skills-sync-now-stores-each-account-s-skills-in-its-own-dire","canonical_anchor":"skills-sync-now-stores-each-account-s-skills-in-its-own-dire","heading":"Skills sync now stores each account's skills in its own directory","tier":"notice","area":"Skills","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/skills-sync-now-stores-each-account-s-skills-in-its-own-dire","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Skills sync now stores each account's skills in its own directory\n\nSynced skills are stored per account, so one account's skills can't mix into another's.\n\n**What**\n\nSyncing skills from the server now first resolves a per-account storage area (a \"bucket\") and does nothing if it cannot. If the directory it resolves to exists but is not marked as belonging to that account, it is moved to a trash area before syncing, so skills from one account cannot be mixed into another's.\n\n**Details**\n\n- No bucket resolves: the round logs and returns early with a distinct outcome, and the end-of-round cleanup sweep is skipped.\n- Unmarked directory found: moved to the trash root, with its own failure event if the move fails.\n- Skill roots, live directories and claim files are all built from the bucket root rather than one shared root.\n- No feature flag guards this in this build; it runs whenever a bucket can be resolved.\n\n**Evidence**\n\n`skills_sync_unmarked_bucket_quarantined`\n\n- Area: Skills\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}