{"version":"2.1.268","anchor":"skills-sync-can-skip-a-full-sync-round-on-startup-if-recentl","canonical_anchor":"skills-sync-can-skip-a-full-sync-round-on-startup-if-recentl","heading":"Skills and plugin sync can skip a redundant round on startup","tier":"use","area":"Skills","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/skills-sync-can-skip-a-full-sync-round-on-startup-if-recentl","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### Skills and plugin sync can skip a redundant round on startup\n\nOn startup, skills and plugin sync now skip a full sync round if one finished recently, controlled by CLAUDE_CODE_SYNC_REUSE_WITHIN_MS\n\n**What**\n\nBoth the skills-sync and plugin-sync processes now accept a `{ startup }` option. When Claude Code starts up (and isn't in cloud\/XD mode, and no sync was force-requested), each of these now checks a saved timestamp to see whether a sync round already completed recently.\n\n- If the last skills sync finished within `CLAUDE_CODE_SYNC_REUSE_WITHIN_MS` milliseconds and the rate-limit \"bucket\" guard hasn't refused it, the sync round is skipped entirely and a `skills_sync_round_reused` event is logged.\n\n- Plugin sync gained an equivalent freshness check; if a recent round is found, it reuses that round instead of re-downloading and re-listing plugins, logging a `plugins_sync_round_reused` event.\n\n**Why**\n\nThis avoids doing redundant sync work (downloading and re-listing skills or plugins) every time Claude Code starts, when a sync already happened moments ago, making startup faster and cheaper without affecting freshness.\n\n- Area: Skills\n- Names: `CLAUDE_CODE_SYNC_REUSE_WITHIN_MS`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 2\/5"}