map-check

Validates knowledge-map scopes against MYK conformance rules via a read-only Node.js checker.

14|1|Updated Jun 14, 2026
One-click install
npx skills add https://github.com/allemaar/open-skills --skill map-check-allemaar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: map-check
Source: https://github.com/allemaar/open-skills/tree/main/skills/map-check
Command: npx skills add https://github.com/allemaar/open-skills --skill map-check-allemaar

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Verifying that an organized knowledge vault still conforms to the Map Your Knowledge (MYK) protocol is tedious and error-prone by hand, and vague "looks fine" verdicts hide real drift. This Skill runs deterministic, read-only conformance checks and always reports exactly what was checked and what was not. ## Core Features & Use Cases - Deterministic conformance checking: A bundled Node.js script validates owner declarations, reciprocal spine links, address forms, frontmatter meta containers, archive consistency, case-fold collisions, exclusion integrity, and link-resolution closure against named MYK rule sources. - Honest verdicts: Unqualified "all clear" results are banned; every report lists the checks run, the inventory source, the mode (FULL or DEGRADED), and the categories not checked. - Fail-closed scope resolution: Ambiguous scopes, unreadable boundaries, and inventory caps produce typed errors rather than false passes. - Use Case: After reorganizing an Obsidian vault, ask the agent to "check this map" to confirm every note still declares a valid owner map and that no dangling or ambiguous links were introduced. ## Quick Start Ask the agent to run map-check on your vault by saying "check this map" or "/map-check" with the target scope path.

Frequently Asked Questions about map-check

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check a knowledge map or vault for conformance issues?

Run the bundled checker with node references/tools/map-check.mjs <target-path> [--json], or ask the agent to "check this map". It validates ownership, links, frontmatter, and archive consistency, returning exit code 0 for qualified-clean, 1 for findings, and 2 or 3 for errors.

What does map-check actually validate in a MYK scope?

It runs nine named checks: owner-declaration, reciprocal-spine, address-form, meta-container, archive-consistency, case-fold-collisions, exclusion-integrity, link-contract-grammar, and link-occurrence-closure. Each finding cites its owning rule file and heading from the map-rules references.

Does map-check modify or repair my files?

No. map-check is read-only forever and never writes, renames, or applies fixes. Confirmed findings are routed to the Handler through the map-this or map-maintain skills, which perform repairs under explicit approval.

Why does map-check never report a simple "all clear"?

The protocol bans unqualified CLEAN verdicts because the checker only covers a defined set of checks. Every report states the checks run, the inventory source and mode, and the categories not checked, such as prose quality and cross-vault validity.

What happens if Node.js or the checker script is unavailable?

No deterministic map-check verdict exists without the companion script. A manual review may follow the map-rules references, but it must be labeled "MANUAL REVIEW — not a map-check verdict" with its exact inventory and omissions stated.

What are the limitations of the map-check checker?

It does not evaluate prose quality, semantic roles, tag semantics beyond syntax, positive cross-vault validity, frontmatter-contained links, optional lifecycle values, or qualified Lyt-vault resolution. Undeclared trees are outside its jurisdiction and absence of a declaration is never a finding.