K-Ops: Skill for Claude Code

Compile Wiki

Goal

Turn source summaries into durable concept pages and keep the navigation layer coherent.

Rules

• Prefer fewer, stronger concept pages over many overlapping pages.
• Merge duplicates instead of proliferating similar pages.
• Keep backlinks reciprocal when possible.
• Preserve uncertainty and provenance.

Desired outcomes

• notes/Concepts/*.md becomes the main knowledge layer.
• notes/Home.md becomes the best navigation entry point.
• notes/TODO.md captures unresolved gaps and follow-up fetches.

Required concept shape

Every compiled concept page must strictly contain the following sections in order:

1. # <Concept Name>
2. ## What It Is
3. ## Why It Matters
4. ## Key Claims
5. ## Related Concepts
6. ## Evidence / Source Basis
7. ## Open Questions (required on every concept page; write at least one question or state _No open questions identified._)
8. ## Backlinks

Citation requirement

Every bullet in ## Key Claims that makes a factual assertion must end with at least one inline source wikilink: ([[Sources/<source_id>|<source_id>]]) or ([[Concepts/<name>|<name>]]).

• supported concept pages require ≥ 90% direct inline citation coverage on claims.
• provisional concept pages require ≥ 70% direct inline citation coverage.
• If a claim cannot be sourced, mark it (unverified) and set claim_quality: provisional.

Contradiction alerts

Before writing or updating a concept page, check data/contradictions.json for entries where concept matches the page stem. If any exist:

1. Set claim_quality: conflicting and evidence_status: contested in the frontmatter.
2. Inject this warning callout immediately after the frontmatter block (before the title and ## What It Is):

   > [!warning] Contradiction
   > This concept has documented conflicting evidence. See `## Open Questions` for details.
   

3. In ## Open Questions, list each contradiction's open_question text as a bullet.