map-rules

Routes Markdown organization operations to required Map Your Knowledge protocol rules before reasoning.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Organizing a Markdown vault or knowledge base without a consistent protocol leads to broken links, duplicate ownership, ambiguous filenames, and lost navigation structure. This Skill forces every organization decision to load the correct Map Your Knowledge (MYK) v2.4 rules before any reasoning or mutation happens. ## Core Features & Use Cases - Rule Routing: Maps each operation type (naming, linking, frontmatter, lifecycle, navigation, ownership) to the exact reference file that must be read first. - Fail-Closed Guards: Blocks ambiguous basenames, duplicate frontmatter keys, multiple owners, and unverified scope verdicts instead of guessing. - Lyt Vault Integration: Handles registered Lyt vaults with proper capture, indexing, and cross-vault citation boundaries. - Use Case: When asked to "organize this vault" or "structure this note", the agent loads scope.md plus the matching route files, confirms the scope contract, and only then proposes or applies organization changes. ## Quick Start Ask the agent to organize your Markdown vault or structure a note, and it will load the required MYK rules before proposing any changes.

Frequently Asked Questions about map-rules

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

FAQPage Schema
How do I organize a Markdown vault with consistent rules?

Invoke this Skill before any organization work. It loads the MYK scope contract first, then routes your specific operation (naming, linking, frontmatter, navigation) to the required reference rules so changes follow one consistent protocol.

What is the Map Your Knowledge protocol for Markdown?

MYK v2.4 is a path-based organization protocol for Markdown covering maps, ownership, metadata, navigation, link resolution, and lifecycle rules. It explicitly excludes sync, dashboards, and durable content identity.

Does this work with Lyt vaults?

Yes. Registered Lyt vaults are detected via the lyt CLI or .lyt/vault.yon, and the Skill uses Lyt-owned capture and indexing operations. It never edits .lyt data, indexes, or sync state directly.

What happens when a Markdown file has ambiguous naming or duplicate owners?

The Skill fails closed. Duplicate basenames, duplicate frontmatter keys, multiple owners, and uncertain targets block the operation and are returned for explicit handler resolution rather than guessed.

When should I not use this Skill?

Do not use it for vault synchronization, topology management, dashboards, or durable content identity. MYK v2.4 explicitly excludes sync and rename-continuity deduplication from its scope.