ariadne:validator

Ariadne Validator

Use this skill when the user asks whether a Markdown knowledge vault is structurally valid, navigable, connected, or ready for ongoing agent use.

Tool

Run the bundled validator from the vault root:

/path/to/skills/validator/scripts/validate_vault.sh

Or pass an explicit vault path:

/path/to/skills/validator/scripts/validate_vault.sh /path/to/vault

For a subtree or its schema-v1 research pipeline, pass a vault-relative scope:

/path/to/skills/validator/scripts/validate_vault.sh /path/to/vault --scope "Domains/Product"
/path/to/skills/validator/scripts/validate_vault.sh /path/to/vault --scope "Domains/Product" --profile research

Scoped runs still inventory the whole vault before filtering findings. --scope rejects absolute paths, traversal, missing paths, and files. --profile research requires a scope; it keeps in-scope YAML, broken-link, orphan, and unlinked-Base failures while excluding sibling-origin defects. Descriptor, hub, and routing findings carry explicit governing obligations when an outside origin directly applies to the selected scope.

The shell wrapper checks for Node.js and delegates to validate_vault.js.

Scope Topology Synchronizer

Resolve scripts/sync_scope_topology.js relative to this installed skill. It is the only scope topology mutation authority. --check is always zero-write and reports findings, proposed changes, complete content_write_paths, and plan_hash:

node /path/to/skills/validator/scripts/sync_scope_topology.js /path/to/vault --check
node /path/to/skills/validator/scripts/sync_scope_topology.js /path/to/vault --check --scope "Domains/Product"

Mutation accepts one exact schema-v1 JSON request:

{"operation_schema":1,"operation":"move","target_scope_id":"alpha","source_path":"Domains/Alpha","destination_path":"Projects/Alpha","normalize_files":[],"allowed_write_paths":["00 Index.md","Agent/Scope Map.md"]}

node /path/to/skills/validator/scripts/sync_scope_topology.js /path/to/vault --write --request /path/to/request.json