From onyx
The frontmatter, naming, and writing rules any agent must follow when creating or editing notes in an Onyx-managed vault. Read this before writing any note, template, or generated text into the vault.
How this skill is triggered — by the user, by Claude, or both
Slash command
/onyx:vault-conventionsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill mirrors `core/conventions/` from the Onyx repository — one source of truth, two audiences (KICKSTART.md §6.2). The bundled reference files carry the full rules:
This skill mirrors core/conventions/ from the Onyx repository — one source of truth, two audiences (KICKSTART.md §6.2). The bundled reference files carry the full rules:
frontmatter.md — the typed-frontmatter schema every framework-created note follows.naming.md — folder styles, what gets transformed when, and the portable-path rules.type (kebab-case class), created (ISO date, set once), status (per-type lifecycle), tags (list, user-owned). Modules add typed fields on top; check the module's docs before inventing a key.Assets/ folder.{{...}} belongs to the Onyx engine and is already resolved by the time files reach the vault; <% tp.* %> belongs to Templater and must be left exactly as written — when you instantiate a template by hand, replace <% ... %> placeholders with real values and leave everything else..vault/lock.json) update themselves; editing one hands ownership to the user and future updates will arrive as *.new siblings. Never move, rename, or delete files you did not create; never touch .vault/ by hand.status changes are value edits, not file moves, unless the module's documented workflow says otherwise.npx claudepluginhub odysseia06/onyx --plugin onyxCreates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.