{"version":"2.1.307","anchor":"context-report-no-longer-shows-a-plugin-name-for-synced-skil","canonical_anchor":"context-report-no-longer-shows-a-plugin-name-for-synced-skil","heading":"Skills from certain repositories now count as synced skills","tier":"notice","area":"Skills","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307\/e\/context-report-no-longer-shows-a-plugin-name-for-synced-skil","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307","markdown":"### Skills from certain repositories now count as synced skills\n\nSkills whose plugin repository matches a check are now treated and reported as `syncedSkills`, and `\/context` drops their plugin name\n\n**What**\n\nSkills are reusable instructions Claude can load. Synced skills are a kind of skill identified by the source `syncedSkills`. Until now, only skills loaded from the syncedSkills folder counted. Now:\n\n- Skills whose plugin repository passes a check are also treated as synced skills, not only those loaded from that folder.\n\n- These skills are reported with the source `syncedSkills` in usage records.\n\n- Skills on a 'following' list are marked with `followsSyncedSkillState`.\n\n- In the context report's skill table, a synced skill no longer shows a plugin name after it. The old code looked at the wrong value, so that name may never have shown correctly.\n\n**Why**\n\nThe way skills from these repositories are labelled and handled changes, and the context report shows them more cleanly.\n\n- Area: Skills\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}