{"version":"2.1.227","anchor":"mcp-skill-caching-survives-more-filesystem-failures","canonical_anchor":"mcp-skill-caching-survives-more-filesystem-failures","heading":"MCP skill caching survives more filesystem failures","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/mcp-skill-caching-survives-more-filesystem-failures","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### MCP skill caching survives more filesystem failures\n\nSkills fetched from MCP servers cache correctly despite permission errors or broken cache folders.\n\n**What**\n\nCaching a skill file fetched from an MCP server now tolerates permission errors (EPERM and EACCES) on rename in addition to the existing already-exists cases, and if an existing cache directory turns out to contain no skill file it is replaced with the freshly fetched copy instead of being left broken. Temporary directories are cleaned up on failure and failed writes now raise a dedicated error.\n\n**Details**\n\n- Where a v5 storage backend is present, the write goes through it instead of the filesystem.\n\n**Evidence**\n\n`MCP skill cache SKILL.md write failed`\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}