{"version":"2.1.312","anchor":"forwarded-mcp-skills-carry-their-name-through-the-skill-tool","canonical_anchor":"forwarded-mcp-skills-carry-their-name-through-the-skill-tool","heading":"Skills passed through from MCP now keep their name and description","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312\/e\/forwarded-mcp-skills-carry-their-name-through-the-skill-tool","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.312","markdown":"### Skills passed through from MCP now keep their name and description\n\nWhen the Skill tool runs a skill passed along from an MCP server, it now carries that skill's name and description\n\n**Unclear.** Where these passed-along MCP skills come from, and whether this is switched on, is not established.\n\n**What**\n\nA skill is a packaged set of instructions Claude can load for a task, and the Skill tool is how Claude uses one. MCP (Model Context Protocol) is a way to connect Claude Code to outside tools and services.\n\nWhen the Skill tool handles a skill passed along from MCP, its result now includes that skill's name. If Claude Code cannot find the skill's description locally, it now uses the description that came with the MCP skill. Before, the description was simply missing.\n\n**Why**\n\nSkills from MCP are now handled by the Skill tool with their name and description intact.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}