compendium-curate

Solid

Use when adding or maintaining a controlled-vocabulary entry in a Compendium-style knowledge store — a cross-cutting glossary/wiki where one concept carries one register-neutral definition + an expert gloss + a plain gloss, and every internal term POINTS to its owning spec instead of restating it. Invoke the moment you are about to write a glossary, a "Terms" section, a "what is X" primer, or a second copy of a definition that already lives in a spec/doc — or when curating an agent knowledge vault and you want the pointer-not-paraphrase + dual-register + first-class-eviction discipline. Portable + runtime-agnostic: plain markdown + frontmatter, works over any vault viewer (a dashboard wiki tab, an Obsidian graph, a provider memory store). For the full normative charter see Compendium.md (this skill is the actionable procedure, not a restatement).

AI & Automation 7 stars 0 forks Updated today Apache-2.0

Install

View on GitHub

Quality Score: 81/100

Stars 20%
30
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Compendium Curate — the pointer-not-paraphrase vocabulary discipline You are about to record vocabulary. A generic note/vault tool will happily let you **paraphrase** a definition that already lives somewhere authoritative — and that copy will rot the moment the source changes. This skill is the *opinion* that a generic vault does not have. The store is plain markdown+frontmatter (any viewer reads it); what you are applying is the **discipline**. ## The one rule (the wedge): pointer-not-paraphrase An **internal-register** entry — a term whose authoritative definition is owned by some spec/doc — carries **a one-line orientation gloss + a pointer to the owner**, and **never** restates the owner's normative content. Restating creates a *second source of truth* that drifts. Compendium is a **source of information, not a source of truth**: authority is one-directional, `entry → owner_spec`. > If you find yourself copying an algorithm, a schema, a score formula, a numbered rule, a payload shape, or a version number — **stop**. Write a one-line gloss and a pointer instead. The **sole exception**: **general-register** vocabulary that *no spec owns* (`owner_spec: null`). For that alone the entry IS the full-definition SSoT (nothing competes, zero conflict). ## Dual register — one concept, two glosses Every entry anchors **one concept** and carries two glosses so a reader at either altitude is served: - **expert** gloss — dense, jargon-OK, for someone who knows the neighborhoo...

Details

Author
SoliEstre
Repository
SoliEstre/EstreGenesis
Created
2 months ago
Last Updated
today
Language
JavaScript
License
Apache-2.0

Similar Skills

Semantically similar based on skill content — not just same category

Code & Development Solid

compendium-lint

Use to gardening-check a Compendium-style controlled-vocabulary store before committing or publishing it — verifying pointer integrity, register discipline, and store health. Invoke after adding/editing entries, on a cadence, or before a release that touches the vocabulary store. Runs the deterministic `lint.cjs` if the runtime is present (`node plugins/compendium/lint.cjs [--reindex]`); otherwise applies the same seven checks by inspection. Portable: the checks are defined over plain markdown+frontmatter, so they hold for any vault (a dashboard store, an Obsidian vault, a provider memory directory). Pairs with `compendium-curate` (curate first, then lint).

7 Updated today
SoliEstre
AI & Automation Listed

foundry

Scaffolds and operates a personal knowledge vault — an agent-maintained wiki in the spirit of Karpathy's LLM wiki and James Bedford's Foundry. Use when the user wants a self-contained, compounding knowledge base where Claude ingests sources (URLs, PDFs, pasted text), writes evergreen concept notes, logs queries with answers, and densifies the wiki over time. Provides slash commands /foundry-init, /foundry-ask, /foundry-triage, /foundry-densify, /foundry-lint.

0 Updated 1 weeks ago
mrheyday
AI & Automation Listed

compile-knowledge

Compile durable knowledge into interlinked-markdown stores the "karpathy method" way — atomic files, [[wiki-links]], a maintained index. Use after producing research, intel, a digest, a learned non-obvious fact, or finishing any knowledge-shaped task, BEFORE you close it. Also when asked to "save this", "write this to the wiki", "update the wiki/memory", "log this finding", "structure this knowledge", or "follow the karpathy method".

1 Updated today
5dive-ai