wiki-synthesizer
Skill0 starsChanged 4 months agoMITView on GitHub
Compiles raw material into the wiki. Automatically preprocesses unstructured journal entries, then promotes ideas into Knowledge/ concept pages and compiles Sources/raw/ into source pages. Updates Maps/_context.md after each run. Use this after learning sessions. Triggers on "synthesize my notes," "compile my wiki," "promote from journal," "process raw sources," and the command /synthesize. Requires the obsidian-vault MCP server connected. Pairs with wiki-operator for on-demand edits and wiki-librarian for maintenance.
In this repository19 other files it gives its agents.
- agent-evalSkill
- agent-redteamSkill
- broadcastSkill
- deid-reid-harnessSkill
- fiction-workshopSkill
- issue-reconcilerSkill
- privacy-linterSkill
- privacy-threat-oracleSkill
- repo-pincerSkill
- research-ledgerSkill
- review-and-planSkill
- style-obfuscatorSkill
- wiki-governorSkill
- wiki-librarianSkill
- wiki-operatorSkill
- wiki-privacy-auditSkill
- wiki-teacherSkill
- wiki-warehouseSkill
- my-skill-nameSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
17 rules. About 0 are common, 6 are distinctive, and 11 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
11
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 18
Distill, don't invent: Only promote ideas explicitly present in journals or raw sources.
- Very specific: line 19
Update over create: Search Knowledge/ before creating any new concept page.
- Distinctive: line 20
Preserve provenance: Every concept page updated during synthesis gets a backlink to the journal entry or source that prompted the update.
- Distinctive: line 21
Non-destructive: When preprocessing journal entries, never delete or rewrite original text — only append structured sections.
- Very specific: line 22
One run, one log: After each synthesis run, append a compact entry to today's run log (Journal/Runs/YYYY-MM-DD.md) documenting what changed.
- Very specific: line 34
Read the journal file. If ## Ideas to promote is already present and non-empty, skip to Phase 1.
- Very specific: line 59
If zero concepts were found, write: (none — content is tasks or transient)
- Distinctive: line 60
If the entry is fewer than three non-trivial lines, flag and skip.
- Very specific: line 66
Read Maps/_context.md to orient.
- Very specific: line 74
If a journal entry has open questions that map to existing concept pages, add them to that page's ## Open questions section.
- Very specific: line 99
Do not fetch, hash, or ingest anything here — this phase only flags.
- Very specific: line 106
Update ## Recently updated with pages touched this run.
- Very specific: line 107
Update ## Open threads — add new drafts, remove anything promoted to mature.
- Very specific: line 113
If today's run log (Journal/Runs/YYYY-MM-DD.md) doesn't exist yet, create it first with write_note (frontmatter type: journal, subtype: …
- Very specific: line 129
If Phase 2.5 found nothing, write (none — no new external citations this run) instead of an empty list.
- Distinctive: line 136
If a journal idea is ambiguous (could map to multiple concept pages), surface the options and ask before promoting.
- Distinctive: line 137
If a raw source is too sparse to compile meaningfully, flag it rather than creating a thin page.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
Wiki Synthesizer
Runs the full raw → wiki pipeline. Handles both unstructured and structured journal entries — if an entry lacks a populated ## Ideas to promote section, the Synthesizer preprocesses it first before promoting. The Synthesizer does not invent — it distills what you already captured.
Prerequisites
The obsidian-vault MCP server must be connected. Verify with /mcp before running.
Note on commands: /synthesize is a natural-language trigger — write it in the chat window as plain text. It is NOT a Claude Code CLI slash command.
Principles
- Distill, don't invent. Only promote ideas explicitly present in journals or raw sources. Never add claims that weren't in the input.
- Update over create. Search
Knowledge/before creating any new concept page. If a page exists, enrich it — do not fork it. - Preserve provenance. Every concept page updated during synthesis gets a backlink to the journal entry or source that prompted the update.
- Non-destructive. When preprocessing journal entries, never delete or rewrite original text — only append structured sections.
- One run, one log. After each synthesis run, append a compact entry to today's run log (
Journal/Runs/YYYY-MM-DD.md) documenting what changed. Never write it into the daily note. - Update the hot cache last.
Maps/_context.mdis written at the end of every run — never mid-run. - Flag citations, don't fetch them. Newly-cited external URLs get surfaced for archival — this skill never fetches or ingests a document itself. That's
wiki-warehouse's job, and its confirm-before-committing rule still applies; flagging is not an ingestion decision.
/synthesize [scope]
Scope options: journal (journals only), sources (raw sources only), or omit to run both.
Phase 0 — Journal preprocessing (conditional)
Runs automatically for each journal entry that lacks a populated ## Ideas to promote section.
- Read the journal file. If
## Ideas to promoteis already present and non-empty, skip to Phase 1. - Scan all content outside existing structured sections. For each fragment, classify:
| Class | Description | Action |
| concept | A durable insight, principle, or model — still useful a month from now | Add to ## Ideas to promote |
| question | Something uncertain or not understood | Add to ## Open questions |
| quote | A verbatim excerpt worth preserving | Add to ## Ideas to promote with > prefix |
| task | Action item or TODO | Leave in place — not wiki content |
| transient | Personal, social, or one-off event | Leave in place — not wiki content |
- Append to the journal entry (never overwrite existing content):
## Ideas to promote
- [Concept name] — [one sentence on what the Knowledge/ page should capture]
## Open questions
- [Question as a complete sentence ending in ?]Rules:
- Extract 2–5 high-quality candidates. Thin lists beat padded ones.
- If zero concepts were found, write:
(none — content is tasks or transient) - If the entry is fewer than three non-trivial lines, flag and skip.
- Stamp frontmatter: add
processed: YYYY-MM-DD. If no frontmatter exists, create a minimal block.
Phase 1 — Journal promotion
- Read
Maps/_context.mdto orient. Note the last synthesis date. - List all journal files in
Journal/Daily/updated since the last synthesis date. - For each journal file:
a. Read the
## Ideas to promotesection (populated by Phase 0 or by the user directly). b. For each idea, searchKnowledge/for an existing concept page. c. If found: add new context, add a backlink to the journal entry, setupdated:to today. d. If not found: create a new page using the concept template, setstatus: draft, link back to the journal entry. e. Mark the promoted idea in the journal: move it to## What I learnedwith→ promoted to [[ConceptPage]]. - If a journal entry has open questions that map to existing concept pages, add them to that page's
## Open questionssection.
Phase 2 — Raw source compilation
- List all files in
Sources/raw/. - For each raw file:
a. Determine type: paper, book, video, article, or note dump.
b. Create a compiled source page in the appropriate
Sources/subfolder using the source template. c. Extract: core argument, key takeaways, quotes worth keeping. d. Link to concept pages inKnowledge/the source references — create stubs (status: draft) for any that don't exist yet. e. Delete the raw file after the compiled page is written. - For any concept stubs created, check whether a page already exists under a different name — merge if so.
Phase 2.5 — External citation flagging
Runs after Phases 1–2 finish, regardless of [scope] — journal promotion and source
compilation can both introduce a bare external URL that has no warehoused backing yet.
- For every page created or updated in Phase 1 or Phase 2 this run, scan its body for
external URLs (
https?://…, in prose or markdown links). - Skip a URL if it's already covered — search
Sources/for a note whose body orwarehouse_path/doc_idfrontmatter corresponds to that same URL. Already-warehoused citations aren't re-flagged every run. - Collect the rest as candidates:
url, the page(s) citing it, and a one-line reason (e.g. "primary source for a confirmed claim" vs. "citation only, unevaluated"). - Do not fetch, hash, or ingest anything here — this phase only flags. Handing a
candidate straight to
wiki-warehouse's/ingestwithout surfacing it first would skip that skill's own confirm-before-committing step.
Phase 3 — Hot cache update
Rewrite Maps/_context.md:
- Update
## Recently updatedwith pages touched this run. - Update
## Open threads— add new drafts, remove anything promoted to mature. - Update
## Vault statscounts. - Set the last synthesis date to today.
Phase 4 — Run log
If today's run log (Journal/Runs/YYYY-MM-DD.md) doesn't exist yet, create it first with write_note (frontmatter type: journal, subtype: run-log, status: draft, confidence: high, updated: <today>; heading # Run log — YYYY-MM-DD), then append — append_note refuses to silently create a frontmatter-less file. Append to today's run log:
## Synthesis run — YYYY-MM-DD
- Preprocessed: [N entries structured]
- Promoted: [[page]], [[page]]
- Compiled sources: [title], [title]
- New stubs: [[page]], [[page]]
- Skipped (already current): [[page]]
## Citations flagged for archival
- <url> — cited in [[page]] (primary source for a confirmed claim) — not yet warehousedIf Phase 2.5 found nothing, write (none — no new external citations this run) instead
of an empty list.
Output discipline
- Report phase-by-phase as you go: "Phase 0: preprocessed 2 entries, found 5 concepts. Phase 1: promoting 5 ideas. Phase 2.5: flagged 3 uncited external URLs for archival."
- List every page to be created or updated before writing it — do not write silently.
- If a journal idea is ambiguous (could map to multiple concept pages), surface the options and ask before promoting.
- If a raw source is too sparse to compile meaningfully, flag it rather than creating a thin page.
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.

