{"version":"2.1.312","anchor":"mcp-loaded-skills-rejected-in-skill-tool-with-unknown-skill","canonical_anchor":"mcp-loaded-skills-rejected-in-skill-tool-with-unknown-skill","heading":"Skills supplied by MCP servers can no longer be run through the Skill tool","tier":"notice","area":"Skills","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312\/e\/mcp-loaded-skills-rejected-in-skill-tool-with-unknown-skill","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312","markdown":"### Skills supplied by MCP servers can no longer be run through the Skill tool\n\nThe Skill tool now refuses skills that come from an MCP server and returns an \"Unknown skill\" error for them\n\n**Unclear.** It is not known whether skills from MCP servers can still be run some other way.\n\n**What**\n\nA skill is a packaged set of instructions Claude can load when a task needs them. Claude runs a skill through the `Skill` tool. An MCP server is a connector that gives Claude extra tools and content.\n\nWhen Claude now tries to run a skill that an MCP server supplied, the `Skill` tool rejects it with an \"Unknown skill\" error. The permission check does the same thing: once your deny rules have been checked, it refuses a skill that came from an MCP server.\n\n**Why**\n\nIf you rely on skills from an MCP server, Claude can no longer start them through the `Skill` tool.\n\n- Area: Skills\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: yes"}