compile-wiki
Skill1 starsChanged 7 months agoMITView on GitHub
Merge source summaries into durable concept pages with backlinks, index entries, and explicit open questions.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- chappyasel/meta-kbtheir own version, first seen Apr 8, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- chappyasel/meta-kb★ 25same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository9 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .codex/AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- ingest-sourcesSkill
- lint-healSkill
- qa-agentSkill
- render-outputSkill
- research-workflowSkill
The file
We split this skill into the rules it gives an agent
12 rules. About 0 are common, 5 are distinctive, and 7 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Prefer fewer, stronger concept pages over many overlapping pages.
- Distinctive: line 14
Keep backlinks reciprocal when possible.
- Distinctive: line 23
Every compiled concept page must strictly contain the following sections in order:
- Very specific: line 34
Every bullet in ## Key Claims that makes a factual assertion must end with at least one inline source wikilink: …
- Very specific: line 37
If a claim cannot be sourced, mark it (unverified) and set claim_quality: provisional.
- Very specific: line 40
Before writing or updating a concept page, check data/contradictions.json for entries where concept matches the page stem.
- Very specific: line 69
Append-only for new manifest nodes: If the manifest gains new nodes since the last ingest, compile may append new ### <section_title> …
- Distinctive: line 71
60 KB warning: Before writing a large source note, check the projected output size.
- Very specific: line 75
Add source_summary_too_large: true to the note's frontmatter.
- Very specific: line 78
Every compilation run must produce a compile log entry before the skill is considered complete.
- Very specific: line 79
Write or append a brief log to research/scratch/compile-YYYYMMDD.md (use today's date) containing:
- Distinctive: line 86
If the file already exists for today, append to it with a timestamp header.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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/*.mdbecomes the main knowledge layer.notes/Home.mdbecomes the best navigation entry point.notes/TODO.mdcaptures unresolved gaps and follow-up fetches.
Required concept shape
Every compiled concept page must strictly contain the following sections in order:
# <Concept Name>## What It Is## Why It Matters## Key Claims## Related Concepts## Evidence / Source Basis## Open Questions(required on every concept page; write at least one question or state_No open questions identified._)## 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>]]).
supportedconcept pages require ≥ 90% direct inline citation coverage on claims.provisionalconcept pages require ≥ 70% direct inline citation coverage.- If a claim cannot be sourced, mark it
(unverified)and setclaim_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:
- Set
claim_quality: conflictingandevidence_status: contestedin the frontmatter. - 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. - In
## Open Questions, list each contradiction'sopen_questiontext as a bullet.
evidence_status & claim_quality
Set evidence_status in frontmatter based on the evidence in ## Evidence / Source Basis:
seed— 0 or 1 sources citedsynthesized— 2+ sources, no contradiction entries indata/contradictions.jsoncontested— any entries exist indata/contradictions.jsonfor this conceptverified— leave as-is if already set by a human reviewer
Set claim_quality in frontmatter based on citation coverage and conflicts:
supported— ≥ 90% citation coverage, no revoked or model-generated backing sources, no conflictsprovisional— citation coverage < 90% but ≥ 70%, or has unverified claimsweak— citation coverage < 70% or sparse evidenceconflicting— contradiction exists indata/contradictions.jsonstale— flagged stale
Large source note contract
See notes/Runbooks/Large_Source_Hierarchy.md for the normative spec. The following rules are binding during compile:
- Human-owned sections in large source notes.
## Document Summaryand## Section Evidence Mapwritten by the ingest-sources skill (or by a human) are treated as human-owned. Compile must not rewrite their prose. Compile may append new###subsections to## Section Evidence Mapwhen new nodes appear in the manifest, but must not alter existing subsection prose. - Append-only for new manifest nodes. If the manifest gains new nodes since the last ingest, compile may append new
### <section_title>blocks to## Section Evidence Map. Existing blocks are read-only (same rule as## Open Questions). - 60 KB warning. Before writing a large source note, check the projected output size. If it would exceed 60 KB (61 440 bytes), emit a compile log entry:
Add[source-note-too-large] <source_id>: <size> bytessource_summary_too_large: trueto the note's frontmatter. Do not truncate silently.
Compile Log Requirement
Every compilation run must produce a compile log entry before the skill is considered complete.
Write or append a brief log to research/scratch/compile-YYYYMMDD.md (use today's date) containing:
- Sources processed (list of source IDs read)
- Pages updated (concept pages that were modified)
- Pages created (new concept pages)
- Contradictions flagged (any new conflicts detected)
- Claims added (new Key Claims entries)
If the file already exists for today, append to it with a timestamp header.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

