What Mindex tells your assistant about the vault, written as a file the CLI reads natively.
Assistant CLIs look for skill files — instructions about the project they are working in. Mindex writes one describing your note types.
Mindex knows what a project is in your vault: which fields it has, which
values status may take, which folder new ones go in, what the filename looks
like. The agent does not. Left to itself it opens a neighbouring note, copies
whatever frontmatter it finds there, and propagates whatever inconsistency it
happened to land on.
The skill file is that knowledge written down in the one place a CLI already looks.
.<assistant>/skills/mindex-note-types/SKILL.md inside the vault — so
.claude/skills/… for Claude Code, and the matching directory for the others.
The file is generated from the types as they are, not as they shipped. Edit a type, add a field, change a set of allowed values, and the regenerated skill describes what you actually have.
The file carries a generator: mindex key in its frontmatter. That is how
Mindex knows the file is its own to overwrite and not something you wrote. Skill
files you author yourself are left alone.