{"version":"2.1.232","anchor":"skill-files-can-be-read-through-a-mounted-memory-store","canonical_anchor":"skill-files-can-be-read-through-a-mounted-memory-store","heading":"Skill files can be read through a mounted memory store","tier":"soon","area":"Skills","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/skill-files-can-be-read-through-a-mounted-memory-store","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Skill files can be read through a mounted memory store\n\nSkills can be discovered from a mounted memory store, with reasons given when one is rejected.\n\n**What**\n\nWhen a memory store and project key are available, skill discovery reads `SKILL.md` through that store instead of resolving it on disk, and reports why a skill was rejected rather than skipping it silently. Without a store mounted, the old disk path is used unchanged.\n\n**Details**\n\n- Typed failures cover a file not at its apparent location, a file moved while being opened, a second name pointing at the same file (skipped for this cycle), and anything that is not a plain small file.\n- Symlink detection moved from calling `isSymbolicLink()` to reading a `symlink` field.\n\n**Evidence**\n\n`is not a plain small file`\n\n- Area: Skills\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}