skills as folders inside dev-brain #6
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
the dev brain (Obsidian vault) setup must also allow to set up a folder inside the vault for skills, so that skills can be managed in Obsidian. Skills are taken into account during the session start, so that the AI knows about them and can pull them in on demand when needed. this should be a full-fledged skill system, just like for example pi implements.
Skills need to be integrated into the default structure as another folder and handled by validation, too. difference only that skills are marked as a skill in the graymatter and that there is a separate index skills.md that lists only verified skills and that is automatically injected into the system prompt.
In general, the skills with pointers to their markdown files are presented in the base prompt at the start of a local session.
Additionally the schema for dev brain should describe skills in a paragraph so the AI can also work on its own skills.
The dev brain preferences need to have a button to recreate purpose.md and schema.md, so that on upgrade we can easily (re)create those files from defaults.
Implemented in
2391e2a. Added a managed skills/ root and generated skills.md, strict type: skill frontmatter with Agent Skills-style name and description rules, existing Dev Brain source provenance/status validation, duplicate-name rejection, and verified-only indexing. Local sessions receive each verified skill's name, description, and Markdown path at startup and in long-context reminders, then read the complete file on demand; changed evidence removes a skill before the next session prompt. Legacy vaults migrate safely, unrelated skills.md notes are never overwritten, generated indexes publish atomically, normal file-tool boundaries include managed skills, and the schema/default docs explain skill authoring. Preferences now has a button that atomically recreates only purpose.md and schema.md while preserving indexes, log, and topics. This is a new DS4Server feature with no DS4 runtime equivalent. Verified with focused migration, validation, stale-evidence, prompt, confinement, and restoration tests plus cargo fmt, Clippy with warnings denied, make bundle, and the full suite: 148 passed, 12 ignored, 0 failed.