{"version":"2.1.296","anchor":"skill-sync-and-gate-changes","canonical_anchor":"skill-sync-and-gate-changes","heading":"Skills can be requested from MCP servers, plus smaller skill sync changes","tier":"notice","area":"Skills","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296\/e\/skill-sync-and-gate-changes","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296","markdown":"### Skills can be requested from MCP servers, plus smaller skill sync changes\n\nClaude Code can send a request to fetch a skill from an MCP server, and skill sync stops early when nothing is readable\n\n**Unclear.** It is not clear how or when Claude Code sends the `skills\/get` request, so whether you can fetch skills from an MCP server yet is unknown.\n\n**What**\n\nSkills are reusable instructions that Claude Code can load for a task. Three smaller changes touch them:\n\n- Claude Code can send a `skills\/get` request, with a skill's address, to an MCP server. MCP servers are outside programs that give Claude Code extra tools and data.\n\n- One skills operation can now stop early when nothing is readable.\n\n- One feature check no longer looks at a fixed list first and relies only on its switch.\n\n**Why**\n\nThe `skills\/get` request suggests that skills could come from MCP servers as well as from local files.\n\n- Area: Skills\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}