wiki-curator

SKILL: Wiki Curator

Maintain the LLM Wiki as a continuously improving knowledge base while preserving FCVW's pillars: updates on demand, measurable freshness, and low token cost.

Purpose

Promote sourced reusable knowledge into the smallest canonical wiki surface without duplicating records or loading the full archive by default.

Activation Triggers

Load this skill when a task involves:

• creating, updating, merging, or reviewing wiki knowledge;
• promoting plans, changelogs, troubleshooting, audits, decisions, or sessions into reusable wiki pages;
• grouping related notes under the same topic;
• organizing tags, themes, or frontmatter colors;
• checking stale, duplicated, contradictory, or superseded wiki content;
• preparing minor or major releases that add reusable knowledge.

Inputs

Changed source records, current canonical page candidates, wiki/README.md, taxonomy, metrics, active index/log, typed relationship findings, stale-source review candidates, and an explicit source-bounded search scope.

Fixed Cost Mode

Always use the standard optimized mode. Do not ask the user to choose a cost mode.

Load only:

1. AGENTS.md checklist summary.
2. CONTEXT_MAP.md row for the active session type.
3. wiki/index.md and wiki/README.md.
4. the taxonomy in wiki/README.md when theme, tag, or freshness decisions are needed.
5. Source files that directly triggered the curation: changed plans, changelogs, troubleshooting records, audits, decisions, sessions, or specific wiki pages.

Do not read every wiki page unless governance-validator (wiki lint mode) reports an anomaly that requires it.

Curation Loop

1. Collect trigger sources: identify new or changed source records and load only their summaries or relevant sections.
2. Decide promotion: promote only knowledge that meets wiki/README.md promotion criteria.
3. Merge before create: update an existing related page when the topic already exists; create a new page only for a distinct reusable concept.
4. Cluster topics: link related pages with Obsidian-style links and record canonical pages for superseded or overlapping notes.
5. Refresh metadata: set last_reviewed, related_version, tags, theme, theme_color, maturity, and next_review when applicable; do not require maturity for source, raw, or session records.
6. Use typed relations deliberately: prefer the narrowest meaningful relation, resolve every target, and rely on generated inverse edges instead of copying both directions.
7. Review changed sources: when a tracked source_digest changes, inspect only pages linked through derived_from; confirm, update, supersede, or invalidate them before refreshing the digest.
8. Update metrics: record freshness, promotion, duplication, source-impact, and taxonomy results in the active plan.
9. Log curation: summarize the curation in the active plan or session note; git history is the log.
10. Validate: run deterministic governance-validator (wiki lint mode) for minor/major releases or when three or more wiki pages changed; semantic review remains optional and source-bounded.