{"version":"2.1.323","anchor":"claudeai-pluginskill-tools-whentouse-text-registry-ids","canonical_anchor":"claudeai-pluginskill-tools-whentouse-text-registry-ids","heading":"Claude gets guidance on when to list or suggest your claude.ai plugins and skills","tier":"notice","area":"Plugins","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/claudeai-pluginskill-tools-whentouse-text-registry-ids","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Claude gets guidance on when to list or suggest your claude.ai plugins and skills\n\nThe tools for listing and suggesting claude.ai plugins and skills gain when-to-use guidance, and sandbox refusals are now reported separately\n\n**What**\n\nClaude has tools that list the claude.ai plugins and skills you have and suggest new ones. Plugins and skills are add-ons that extend what Claude can do. These tools changed in three ways:\n\n- They now carry guidance on when to use them, for example for when you ask which claude.ai skills you already have enabled.\n\n- They now carry an ID that identifies each tool in a registry.\n\n- A list can now come back with a note saying it stopped at a page limit.\n\nSometimes the search or list service refuses a request and the tool falls back to an empty result. Before, that was always recorded as your account not being entitled to the feature. A refusal that comes from a sandbox, meaning a restricted environment that blocks certain access, is now recorded as a sandbox refusal.\n\n**Why**\n\nThe guidance helps Claude choose the right tool when you ask about your plugins and skills. Keeping sandbox refusals separate from entitlement failures means an empty list is no longer always put down to your account.\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}