{"version":"2.1.223","anchor":"user-scope-skills-and-dynamic-workflows-can-be-read-and-writ","canonical_anchor":"user-scope-skills-and-dynamic-workflows-can-be-read-and-writ","heading":"User-scope skills and dynamic workflows can be read and written through the storageV5 backend","tier":"soon","area":"Skills","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223\/e\/user-scope-skills-and-dynamic-workflows-can-be-read-and-writ","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223","markdown":"### User-scope skills and dynamic workflows can be read and written through the storageV5 backend\n\nYour skills and saved workflows can be read and written through a pluggable storage backend instead of local files.\n\n**What**\n\nSkill scanning and workflow saving can route through a pluggable storage backend instead of the local filesystem, which is the groundwork for host-managed and remote storage sessions.\n\n**Details**\n\n- The skill scanner takes an optional storageV5 backend; for the user skills directory it lists entries through the backend.\n- For any other base directory it logs a warning and falls back to the filesystem scan.\n- Directory listing for user settings routes through the backend the same way, and workflow saving writes via `userConfigDir(\"workflows\", ...)` with an ifAbsent precondition when not overwriting.\n- Inactive unless a storageV5 backend is handed in; without one everything stays on the raw filesystem path.\n\n**Evidence**\n\n`falling back to the raw scan`\n\n- Area: Skills\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}