メニュー
Validate vault files against .mdschema files — structural checks on frontmatter, headings, and required sections. USE WHEN validate vault, check vault, vault lint, schema check, validate journals, validate memory.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Resolve Obsidian Base files (.base) to see what the user sees in Obsidian. USE WHEN the user asks about Base views, queries vault notes, wants to see what a .base file shows, or needs filtered/sorted vault data. Wraps the obsidian-base CLI.
Vault conventions for wikilinks, frontmatter and tags. USE WHEN working with Obsidian vault files.
Obsidian template management — dual-tree creation, editing, rendering, frontmatter schemas, dynamic query blocks, Templater config updates. USE WHEN creating templates, editing templates, rendering templates, modifying template schemas, updating Templater folder mappings, adding query blocks, or checking template compliance.
Add [[wikilinks]] to a markdown document by matching terms against existing vault notes — body links and frontmatter keywords/related enrichment. USE WHEN a document needs wikilinks, terms should link to vault notes, knowledge graph needs enrichment, or enrich keywords.
[DEPRECATED] Use /ObsidianCLI instead. Obsidian Actions URI — atomic frontmatter props-set, rename with backlink updates, create notes, open notes. USE WHEN Obsidian Actions, actions URI, property set, rename note.
Official Obsidian CLI (1.12+) — list files, search content, manage properties, query bases, navigate links, create/read/rename/delete notes. USE WHEN listing vault files, searching vault, managing frontmatter properties, querying bases, checking backlinks, creating notes via Obsidian, renaming with backlink updates, or any vault operation that benefits from Obsidian's internal index.
| name | ValidateVault |
| version | 0.1.0 |
| description | Validate vault files against .mdschema files — structural checks on frontmatter, headings, and required sections. USE WHEN validate vault, check vault, vault lint, schema check, validate journals, validate memory. |
Validate vault markdown files against .mdschema schema files using the mdschema CLI. Reports structural violations: missing frontmatter fields, wrong field types, unexpected headings, missing required sections.
| Workflow | Trigger | Section |
|---|---|---|
| Check | "validate vault", "check journals", "validate memory" | Check |
| Report | "how bad is it", "vault health", "show violations" | Report |
Binary: mdschema (Go, installed via brew install jackchuka/tap/mdschema).
mdschema check "glob/pattern/**/*.md" --schema path/to/.mdschema
Output: per-file list of ✗ violations with line numbers, categories ([frontmatter], [structure]), and descriptions.
Schemas ship with their convention-owning module, not in the vault. The vault contains instances; modules contain the rules.
| Content | Schema Location | Vault Glob |
|---|---|---|
| Daily journals | $VAULT/Templates/Journals/.mdschema | $VAULT/Resources/Journals/Daily/**/*.md |
| Weekly journals | $VAULT/Templates/Journals/.mdschema | $VAULT/Resources/Journals/Weekly/**/*.md |
| Memory Insights | $MODULES/forge-reflect/skills/MemoryInsights/Templates/.mdschema | $VAULT/Orchestration/Memory/Insights/*.md |
| Memory Imperatives | $MODULES/forge-reflect/skills/MemoryInsights/Templates/.mdschema | $VAULT/Orchestration/Memory/Imperatives/*.md |
| Memory Ideas | $MODULES/forge-reflect/skills/MemoryInsights/Templates/.mdschema | $VAULT/Orchestration/Memory/Ideas/*.md |
Where $VAULT resolves from user.root in config.yaml (currently Vaults/Personal) relative to $HOME/Data, and $MODULES is Modules/.
Resolve the vault root from config.yaml:
FORGE_ROOT="$HOME/Data"
VAULT="$FORGE_ROOT/$(grep 'root:' "$FORGE_ROOT/config.yaml" | awk '{print $2}')"
MODULES="$FORGE_ROOT/Modules"
Verify mdschema is installed:
command -v mdschema >/dev/null || { echo "mdschema not installed — brew install jackchuka/tap/mdschema"; exit 1; }
Determine scope from user request. Default to journals if unspecified.
Run validation against the relevant schema:
# Daily journals
mdschema check "$VAULT/Resources/Journals/Daily/**/*.md" \
--schema "$VAULT/Templates/Journals/.mdschema"
# Weekly journals
mdschema check "$VAULT/Resources/Journals/Weekly/**/*.md" \
--schema "$VAULT/Templates/Journals/.mdschema"
# Memory (when requested)
mdschema check "$VAULT/Orchestration/Memory/Insights/*.md" \
--schema "$MODULES/forge-reflect/skills/MemoryInsights/Templates/.mdschema"
Present results to the user grouped by violation type.
Summarize validation results as a structured report:
Run the Check workflow, capturing full output.
Count violations by category:
Present summary table:
| Directory | Files | Passing | Failing | Top Violation |
|---------------|-------|---------|---------|-------------------------|
| Daily 2026/01 | 31 | 12 | 19 | missing "## Plan" |
| Daily 2026/02 | 27 | 25 | 2 | missing 'tlp' field |
| Weekly 2026 | 8 | 8 | 0 | — |
List the top 5 most common violations with counts.
Suggest remediation approach (batch fix vs manual).
mdschema is not installed — report the missing dependency..mdschema currently lives in the vault (Templates/Journals/). Future: migrate to forge-journals as source of truth.mdschema validates structure only — it cannot check semantic correctness (enum values, tag formats, date validity).