nguyenvanduocit/claude-code-vault-keeper/vault-help

vault.help — what claude-code-vault-keeper can do

This skill prints a help overview. It runs nothing and edits nothing — it only renders the block below and, if asked, points the user at the right doc.

Step 1 — confirm the skill list is current (silent)

Run ls "${CLAUDE_PLUGIN_ROOT:-.}/skills" (or ls skills from the plugin root). If the directory listing differs from the table below — a skill was added or removed since this file was last edited — render the live listing instead and mention the help table is stale so it gets fixed.

Step 2 — render the help

Present this block to the user. Keep the GitHub links intact; they are how the user reaches the full docs.

claude-code-vault-keeper — template-driven markdown validation for a knowledge vault. Documents point at a template; templates declare their own schema (fields: + body section-rules); the engine enforces whatever it finds. The plugin knows nothing about your domain words.

Skills — type any of these in a Claude session:

CLI — run from the project root:

• vault-keeper validate — validate every document against its template (--json for structured output; exit code is non-zero on errors).
• vault-keeper doctor — check environment + config state (--json supported).

Documentation — full guides on GitHub:

Repository: <https://github.com/nguyenvanduocit/claude-code-vault-keeper>

Setup

• Getting started
• Vault config — .claude/vault-keeper.json

Authoring templates

• Templates overview
• Frontmatter rules
• Folder & filename rules
• Body rules
• Full example

Running the validator

• CLI validator
• LSP features
• Programmatic usage
• CI/CD integration

Reference

• Canonical formatter
• Naming conventions
• Architecture
• Troubleshooting

Step 3 — answer the follow-up

If the user named a topic (e.g. "how do I write a template", "fix is failing"), point them at the single most relevant doc link above and offer the matching skill — don't paste the doc contents.