Wiki synthesizer
Portable AI agent skills built on the open SKILL.md standard — self-contained capabilities any compatible agent can discover and load on demand, usable across Claude, Codex, Gemini CLI, Cursor, and GitHub Copilot.
npx -y skills add Hefrock/agent-skills --skill wiki-synthesizerAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
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.
SKILL.md
5.8 KB, as published. Nobody here has run it
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 journal documenting what changed.
- Update the hot cache last.
Maps/_context.mdis written at the end of every run — never mid-run.
/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 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
Append to today's journal:
## Synthesis run — YYYY-MM-DD
- Preprocessed: [N entries structured]
- Promoted: [[page]], [[page]]
- Compiled sources: [title], [title]
- New stubs: [[page]], [[page]]
- Skipped (already current): [[page]]
Output discipline
- Report phase-by-phase as you go: "Phase 0: preprocessed 2 entries, found 5 concepts. Phase 1: promoting 5 ideas."
- 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.