Claude Skill

map-check

The honest inspector for Map Your Knowledge — read-only conformance checks of an organized scope via a small bundled script, always reporting what was checked AND what was not; it can never claim an unqualified "all clear". Trigger when the user says "check this map", "check the

LLM Mart · 0 points · 0 views 0 listing impressions 0 install-command copies
Download allemaar-open-skills-skills_map-check-acf5f79.zip · 18 KB

Install

skills CLI npx skills add https://github.com/allemaar/open-skills/tree/main/skills/map-check
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install allemaar-open-skills@llmmart
Git git clone https://github.com/allemaar/open-skills.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole allemaar/open-skills collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

/map-check

The read-only conformance front door for Map Your Knowledge (MYK). It validates a scope against the named MYK sources and never invents rules of its own.

Protocol provenance. MYK v2.4 comes from map-rules/SKILL.md and its routed references. Each finding carries its owning file and heading.

The two iron rules

  1. Read-only forever. map-check never writes, renames, or proposes-and-applies. Findings go to the Handler, and repairs run through map-this (one-off) or map-maintain (the tending loop).
  2. Unqualified CLEAN is banned. The only positive verdict is: "clean for checks over inventory , mode ; not checked: ." A crash can never read as a pass: the JSON envelope separates operational errors from findings by shape.

Load the available map-rules owner and selected references for manual rule/provenance review. If that sibling is absent, the bundled compiled checker may still run within its documented boundary; report manual rule review unavailable, never invent the missing rules or claim full coverage.

Required checker companion

The bundled deterministic companion references/tools/map-check.mjs does the mechanical work with Node.js and no model in the validation path:

node <this-skill>/references/tools/map-check.mjs <target-path> [--root-map <scope-relative-path>] [--json] [--max-files N] [--max-ms N]
  • Target classes: an explicit path inside a scope, or a scope root (a directory containing .myk/README.md or a declared root map). Ambiguous or contested scopes fail closed (scope-conflict).
  • DEGRADED target: pass the established scope root itself as <target-path> and its contained root-map locator through --root-map. The checker resolves that locator relative to the supplied target; it does not promise walk-up scope discovery from a nested target.
  • Modes: FULL when scope.md — Organized-scope evidence resolves .myk/README.md; DEGRADED when the caller supplies another exact declared root-map source. Absence of a declaration is never a finding; undeclared trees are outside jurisdiction.
  • Inventory honesty: the script checks the supplied target, scope root and required read paths with lstat and native-realpath identity before use, then walks the scope with bounded inventory. Every governed Markdown entrypoint must be readable, including when reached only by a plain link without a fragment. Visible redirects, unreadable required evidence and skipped boundaries produce operationally incomplete exit 2. These mechanisms cannot observe every reparse form and do not prevent races; the result is not proof of race-free containment. The report includes inventory: {source, complete, scanned}.
  • Exit codes: 0 ran, zero findings (qualified-clean) · 1 ran, findings present · 2 operational error · 3 target/scope resolution error.

Checks

Check Named source Finding classes
owner-declaration ownership.md — Eligibility and ownership missing-owner · multiple-owners · root-declares-owner
reciprocal-spine ownership.md — Eligibility and ownership spine-drift-mapside · dangling-owner
address-form naming.md — Address rules and lyt.md — Cross-vault references bare-duplicate-basename · ambiguous-target · raw-cross-vault-wikilink
meta-container frontmatter.md — Additional constraints and ownership.md — Shared meta parse-error · duplicate-key · malformed-map-value · legacy-owner-key
archive-consistency lifecycle.md — Currentness and archive evidence missing-callout · signal-disagreement · unsignalled-archive
case-fold-collisions naming.md — Sibling case-fold collisions case-fold-collision
exclusion-integrity ownership.md — Managed artifacts and ownership.md — Excluded subtrees malformed-exclusion · mapside-coverage-missing
link-contract-grammar link-resolution.md — Scope-contract grammar malformed-contract
link-occurrence-closure link-resolution.md — Terminal classes and closure occurrence-closure-broken

Not checked, reported every run: prose quality; semantic roles in free-form maps; earned-scope judgment; whether an undeclared tree should be organized; tag semantics beyond syntax; positive cross-vault validity; frontmatter-contained links; optional lifecycle-value legality; snapshot exemptions; the eight-field frontmatter ceremony; qualified Lyt-vault target resolution; and work state.

Bundled checker boundary

The companion implements the named checks above, with address-form limited to owner resolution, duplicate-basename ambiguity, and raw cross-vault prohibition. It independently parses link declarations and resolves the eleven terminal occurrence classes from link-resolution.md. A cap before inventory or occurrence closure returns typed check-incomplete exit 2, never clean. Invalid machine declarations return contract-invalid with diagnostics and no usable resolution. After occurrence closure, a time cap assigns the remaining records residual-at-cap, emits incomplete resolution and exit 1; do not heal or enrich from it. map-scan and map-check share named semantics but no implementation; normalized-record disagreement is evidence.

Not implemented: optional lifecycle values, eight-field ceremony, snapshot pairs, automatic discovery of scope-local instructions, Unicode/Obsidian heading-slug normalization, embed-specific semantics, and qualified-Lyt-vault resolution. Narrowing the declared boundary requires explicit review.

Suppression sources — exactly two

The script consumes only M3 declarations in the scope contract: exclusions_honored and managed_declared identify their source paths under ownership.md. It does not load style records or suppress findings from prose. A Handler-confirmed style ruling may be applied only in a separate manual disposition ledger naming the ruling source, affected finding and reason; relay the raw deterministic verdict unchanged. Unknown or unconfirmed prose suppresses nothing.

Agent duties around the script

Run it and relay its verdict intact. Never upgrade "clean for these checks" into "all clear". Lead with DEGRADED mode or incomplete inventory. Route findings to the Handler through map-this or map-maintain.

If Node.js or the exact checker companion is unavailable, no deterministic map-check verdict exists. A separate review may follow the selected map-rules references, but label it MANUAL REVIEW — not a map-check verdict, state its exact inventory and omissions, and never issue qualified-clean language.

Human output. This skill's handler-facing output obeys the human-output contract (human-output/SKILL.md).

Next skills. On completion, run the Next Skills protocol (next-skills/SKILL.md): surface the next-skills recommendations from front-matter for the caller to pick. Offer only — never auto-invoke.

Self-improvement. On completion, run the Self-Improvement Protocol (self-improve/SKILL.md): apply its signal taxonomy and threshold to this run; surface any surviving proposal for handler approval. Conservative — silent otherwise. Never auto-apply.

Files (open-skills)
  • references
    • tools
      • map-check.mjs 46.8 KB · in bundle
  • SKILL.md 8.9 KB
    ---
    name: map-check
    description: The honest inspector for Map Your Knowledge — read-only conformance checks of an organized scope via a small bundled script, always reporting what was checked AND what was not; it can never claim an unqualified "all clear". Trigger when the user says "check this map", "check the graph", "is this vault still healthy", "run map-check", or "/map-check". Read-only forever; repairs belong to map-this and map-maintain.
    visibility: public
    self-improvable: true
    triggers:
      - "/map-check"
      - "check this map"
      - "check the graph"
      - "is this vault healthy"
    next-skills:
      - skill: map-maintain
        phrase: "/map-maintain"
        why: "Run one Handler-gated repair-and-recheck cycle for confirmed findings."
      - skill: map-this
        phrase: "/map-this"
        why: "Re-organize or extend the scope the check just measured."
    ---
    
    # /map-check
    
    The read-only conformance front door for **Map Your Knowledge (MYK)**. It validates a scope against the named MYK sources and never invents rules of its own.
    
    > **Protocol provenance.** MYK v2.4 comes from [`map-rules/SKILL.md`](../map-rules/SKILL.md) and its routed references. Each finding carries its owning file and heading.
    
    ## The two iron rules
    
    1. **Read-only forever.** map-check never writes, renames, or proposes-and-applies. Findings go to the Handler, and repairs run through `map-this` (one-off) or `map-maintain` (the tending loop).
    2. **Unqualified CLEAN is banned.** The only positive verdict is: *"clean for checks {list} over inventory {source}, mode {mode}; not checked: {list}."* A crash can never read as a pass: the JSON envelope separates operational errors from findings by shape.
    
    Load the available `map-rules` owner and selected references for manual rule/provenance review. If that sibling is absent, the bundled compiled checker may still run within its documented boundary; report manual rule review unavailable, never invent the missing rules or claim full coverage.
    
    ## Required checker companion
    
    The bundled deterministic companion [`references/tools/map-check.mjs`](references/tools/map-check.mjs) does the mechanical work with Node.js and no model in the validation path:
    
    ```bash
    node <this-skill>/references/tools/map-check.mjs <target-path> [--root-map <scope-relative-path>] [--json] [--max-files N] [--max-ms N]
    ```
    
    - **Target classes:** an explicit path inside a scope, or a scope root (a directory containing `.myk/README.md` or a declared root map). Ambiguous or contested scopes fail closed (`scope-conflict`).
    - **DEGRADED target:** pass the established scope root itself as `<target-path>` and its contained root-map locator through `--root-map`. The checker resolves that locator relative to the supplied target; it does not promise walk-up scope discovery from a nested target.
    - **Modes:** FULL when [`scope.md` — Organized-scope evidence](../map-rules/references/scope.md#organized-scope-evidence) resolves `.myk/README.md`; DEGRADED when the caller supplies another exact declared root-map source. Absence of a declaration is never a finding; undeclared trees are outside jurisdiction.
    - **Inventory honesty:** the script checks the supplied target, scope root and required read paths with lstat and native-realpath identity before use, then walks the scope with bounded inventory. Every governed Markdown entrypoint must be readable, including when reached only by a plain link without a fragment. Visible redirects, unreadable required evidence and skipped boundaries produce operationally incomplete exit `2`. These mechanisms cannot observe every reparse form and do not prevent races; the result is not proof of race-free containment. The report includes `inventory: {source, complete, scanned}`.
    - **Exit codes:** `0` ran, zero findings (qualified-clean) · `1` ran, findings present · `2` operational error · `3` target/scope resolution error.
    
    ## Checks
    
    | Check | Named source | Finding classes |
    |---|---|---|
    | `owner-declaration` | [`ownership.md` — Eligibility and ownership](../map-rules/references/ownership.md#eligibility-and-ownership) | missing-owner · multiple-owners · root-declares-owner |
    | `reciprocal-spine` | [`ownership.md` — Eligibility and ownership](../map-rules/references/ownership.md#eligibility-and-ownership) | spine-drift-mapside · dangling-owner |
    | `address-form` | [`naming.md` — Address rules](../map-rules/references/naming.md#address-rules) and [`lyt.md` — Cross-vault references](../map-rules/references/lyt.md#cross-vault-references) | bare-duplicate-basename · ambiguous-target · raw-cross-vault-wikilink |
    | `meta-container` | [`frontmatter.md` — Additional constraints](../map-rules/references/frontmatter.md#additional-constraints) and [`ownership.md` — Shared meta](../map-rules/references/ownership.md#shared-meta) | parse-error · duplicate-key · malformed-map-value · legacy-owner-key |
    | `archive-consistency` | [`lifecycle.md` — Currentness and archive evidence](../map-rules/references/lifecycle.md#currentness-and-archive-evidence) | missing-callout · signal-disagreement · unsignalled-archive |
    | `case-fold-collisions` | [`naming.md` — Sibling case-fold collisions](../map-rules/references/naming.md#sibling-case-fold-collisions) | case-fold-collision |
    | `exclusion-integrity` | [`ownership.md` — Managed artifacts](../map-rules/references/ownership.md#managed-artifacts) and [`ownership.md` — Excluded subtrees](../map-rules/references/ownership.md#excluded-subtrees) | malformed-exclusion · mapside-coverage-missing |
    | `link-contract-grammar` | [`link-resolution.md` — Scope-contract grammar](../map-rules/references/link-resolution.md#scope-contract-grammar) | malformed-contract |
    | `link-occurrence-closure` | [`link-resolution.md` — Terminal classes and closure](../map-rules/references/link-resolution.md#terminal-classes-and-closure) | occurrence-closure-broken |
    
    **Not checked, reported every run:** prose quality; semantic roles in free-form maps; earned-scope judgment; whether an undeclared tree should be organized; tag semantics beyond syntax; positive cross-vault validity; frontmatter-contained links; optional lifecycle-value legality; snapshot exemptions; the eight-field frontmatter ceremony; qualified Lyt-vault target resolution; and work state.
    
    ## Bundled checker boundary
    
    The companion implements the named checks above, with address-form limited to owner resolution, duplicate-basename ambiguity, and raw cross-vault prohibition. It independently parses link declarations and resolves the eleven terminal occurrence classes from [`link-resolution.md`](../map-rules/references/link-resolution.md). A cap before inventory or occurrence closure returns typed `check-incomplete` exit `2`, never clean. Invalid machine declarations return `contract-invalid` with diagnostics and no usable resolution. After occurrence closure, a time cap assigns the remaining records `residual-at-cap`, emits incomplete resolution and exit `1`; do not heal or enrich from it. `map-scan` and `map-check` share named semantics but no implementation; normalized-record disagreement is evidence.
    
    Not implemented: optional lifecycle values, eight-field ceremony, snapshot pairs, automatic discovery of scope-local instructions, Unicode/Obsidian heading-slug normalization, embed-specific semantics, and qualified-Lyt-vault resolution. Narrowing the declared boundary requires explicit review.
    
    ## Suppression sources — exactly two
    
    The script consumes only M3 declarations in the scope contract: `exclusions_honored` and `managed_declared` identify their source paths under `ownership.md`. It does not load style records or suppress findings from prose. A Handler-confirmed style ruling may be applied only in a separate manual disposition ledger naming the ruling source, affected finding and reason; relay the raw deterministic verdict unchanged. Unknown or unconfirmed prose suppresses nothing.
    
    ## Agent duties around the script
    
    Run it and relay its verdict intact. Never upgrade "clean for these checks" into "all clear". Lead with DEGRADED mode or incomplete inventory. Route findings to the Handler through `map-this` or `map-maintain`.
    
    If Node.js or the exact checker companion is unavailable, no deterministic map-check verdict exists. A separate review may follow the selected `map-rules` references, but label it `MANUAL REVIEW — not a map-check verdict`, state its exact inventory and omissions, and never issue qualified-clean language.
    
    > **Human output.** This skill's handler-facing output obeys the human-output
    > contract (`human-output/SKILL.md`).
    
    > **Next skills.** On completion, run the Next Skills protocol (`next-skills/SKILL.md`): surface the `next-skills` recommendations from front-matter for the caller to pick. Offer only — never auto-invoke.
    
    > **Self-improvement.** On completion, run the Self-Improvement Protocol (`self-improve/SKILL.md`): apply its signal taxonomy and threshold to this run; surface any surviving proposal for handler approval. Conservative — silent otherwise. Never auto-apply.
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.