knowledge

name	knowledge
description	Find and maintain the user's knowledge notes. Use to locate which knowledge notes are relevant to a task (run the map tool for progressive disclosure), or when creating, updating, or organizing a domain note. Authority on MUM's knowledge-note format. Do not use for editing the constitution (AGENTS.md) or building skills (see skill-builder).

Knowledge

You find and maintain MUM's knowledge — the markdown notes about the user. Core notes at the root of knowledge/ (user.md, mum.md) are always read. Everything else is a domain note in a life/work-area subfolder, loaded only when relevant.

Finding relevant notes (progressive disclosure)

Don't read every note to figure out what's relevant. Run the map tool — it prints each domain note's frontmatter (so you read only the descriptions, not whole files), then open just the notes that match the task:

python .agents/skills/knowledge/scripts/map.py        # readable lines
python .agents/skills/knowledge/scripts/map.py --json  # structured
python .agents/skills/knowledge/scripts/map.py --help

Domain-note format

A domain note is a markdown file in a knowledge/<domain>/ subfolder with YAML frontmatter, then freeform notes:

---
name: <short human-readable name>
description: <what it covers and when to read it — this is the routing line the map shows>
version: 1
---

# <Title>

<concise notes — facts over prose, one topic per file>

• description is the most important field: it's all the map shows, so make it a precise "what it covers + when to read it". Keep it to a line.
• version is a plain integer, starting at 1. Bump it on a meaningful change — it's a memorable handle for referring back or rolling back. Don't track a date; the map derives last-updated from git automatically.

Creating or updating a note

1. Pick the right knowledge/<domain>/ subfolder (create one only when a real domain emerges). Use a clear filename.
2. Write the frontmatter (name, description, version) and concise notes.
3. On a meaningful revision, bump version.
4. Commit to main.

Gotchas

• Keep description accurate when the note's content shifts — it's the only thing the map surfaces, so a stale description misroutes.
• One topic per note; split a note that grows two distinct concerns rather than padding it.