{"version":"2.1.299","anchor":"mcp-servers-can-now-expose-skills-verified-by-digest-and-lo","canonical_anchor":"mcp-servers-can-now-expose-skills-verified-by-digest-and-lo","heading":"MCP servers can provide skills, checked before they are loaded","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/mcp-servers-can-now-expose-skills-verified-by-digest-and-lo","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### MCP servers can provide skills, checked before they are loaded\n\nClaude Code can load skills listed by MCP servers, checking each one's size and fingerprint against the server's list first\n\n**Unclear.** It is not clear whether loading skills from MCP servers is switched on by default.\n\n**What**\n\nA skill is a packaged set of instructions, kept in a `SKILL.md` file, that Claude can use for a particular kind of task. Claude Code can now load skills that an MCP server lists. An MCP server is an outside program that gives Claude Code extra tools.\n\n- Checking: each skill's `SKILL.md` is read from the server and must match the server's own listing in size, in its sha256 fingerprint (a code calculated from the file's exact contents) and in its frontmatter (the header at the top of the file).\n\n- Caching: copies already saved are reused.\n\n- Rejects: skills that fail a check are reported with the reason.\n\n- Names: each skill is named after its server, and clashing names are told apart.\n\nIf a server changes a skill or stops providing it, Claude Code tells you to reconnect the server from `\/mcp` to refresh its skills.\n\n**Why**\n\nMCP servers become a new source of skills. The fingerprint check means a skill is only loaded if its contents match what the server listed.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 5\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}