mycowrite-myco-skilllisted

# Writing a Myco-Managed Skill A Myco-managed skill is a SKILL.md file with YAML frontmatter that Claude Code reads to decide whether to load procedural context. The `vault_write_skill` agent tool writes the file to disk, creates or updates the skill record in the vault database, and bumps the generation counter. ## Prerequisites - An approved skill candidate (from `vault_skill_candidates`) or a specific skill to update - A clear scope: one procedure, one context — not a broad reference document - The skill name in kebab-case (e.g., `register-mcp-tool`, `add-vault-table`) ## Frontmatter Structure Every SKILL.md must open with a YAML frontmatter block containing all six required fields: ```yaml --- name: myco:<kebab-case-name> description: <triggering description> managed_by: myco user-invocable: true allowed-tools: - Read - Edit - Write - Bash - Grep - Glob --- ``` ### Field Reference **`name`** — Must use the `myco:` prefix (e.g., `myco:add-vault-table`). The kebab-case portion must match the directory name under `.agents/skills/`. Do not use `/`, `\`, or `..` in the name — the path security gate rejects these before any filesystem operation. **`description`** — The primary triggering mechanism. Claude Code reads this to decide whether to load the skill. Write it to be specific and pattern-rich: - Name the exact conditions that should trigger the skill - Include related component names, file paths, and tool names - Cover edge cases and indirect triggers