
Wiki Digest
Turn recent Obsidian wiki edits into a readable weekly-style digest of what you learned and which themes emerged.
Install
npx skills add https://github.com/ar9av/obsidian-wiki --skill wiki-digestWhat is this skill?
- Newsletter-style knowledge digest distinct from wiki-status source-ingestion deltas
- Parses daily, weekly, monthly, since-date, or custom day ranges from natural language
- Resolves Obsidian vault path via llm-wiki config protocol (.env, ~/.obsidian-wiki/config)
- Summarizes learned themes, updates, and connections—not just file churn
- Triggered by phrases like weekly summary, knowledge report, and /wiki-digest
Adoption & trust: 1k installs on skills.sh; 1.8k GitHub stars; 3/3 security scanners passed (skills.sh audits).
Recommended Skills
Grill Memattpocock/skills
Grill With Docsmattpocock/skills
Brainstormingobra/superpowers
Lark Tasklarksuite/cli
Lark Workflow Standup Reportlarksuite/cli
Cavemanjuliusbrussee/blueprint
Journey fit
Primary fit
Grow/content is the canonical shelf because the output is a human newsletter summarizing knowledge compounding, not raw ingestion telemetry. Content subphase fits periodic summaries meant for review, sharing, and editorial follow-ups.
Common Questions / FAQ
Is Wiki Digest safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.
SKILL.md
READMESKILL.md - Wiki Digest
# Wiki Digest — Knowledge Newsletter Generator You are generating a human-readable digest of recent wiki activity: what was learned, what was updated, what themes are emerging, and what's worth reviewing. This skill summarizes *knowledge*, not sources — think of it as a weekly review session, not an ingestion status report. ## Before You Start 1. **Resolve config** — follow the Config Resolution Protocol in `llm-wiki/SKILL.md` (walk up CWD for `.env` → `~/.obsidian-wiki/config` → prompt setup). This gives `OBSIDIAN_VAULT_PATH` and `OBSIDIAN_LINK_FORMAT`. 2. **Parse the period** from the user's request: - "daily" / "today" / "yesterday" → last 24 hours - "weekly" / "this week" / no argument (default) → last 7 days - "monthly" / "this month" → last 30 days - ISO date like "since 2026-05-01" → pages updated since that date - Explicit number like "last 14 days" → that many days 3. Read `$OBSIDIAN_VAULT_PATH/log.md` — last 200 lines — for entries within the period (timestamps are ISO-8601 prefixed lines). 4. Read `$OBSIDIAN_VAULT_PATH/hot.md` for current session context. 5. If `$OBSIDIAN_VAULT_PATH/_insights.md` exists, read its **Anchor Pages** table — you'll use it later to identify which new pages became hubs. ## Step 1: Collect Pages Active in the Period Glob all `.md` files under `$OBSIDIAN_VAULT_PATH`. Skip special/system files: - `index.md`, `log.md`, `hot.md`, `AGENTS.md`, `_insights.md` - Anything under `_meta/`, `_archives/`, `_raw/` - Journal digest pages themselves (`journal/digest-*.md`) For each remaining page, read its frontmatter: - `created` — when the page was first written - `updated` — when it was last modified Classify: - **New pages**: `created` is within the period - **Updated pages**: `updated` is within the period but `created` is before it - **Unchanged**: neither date falls in the period → skip If fewer than 5 pages were active, note it and offer to widen: *"Only 3 pages were active in the last 7 days — want a monthly digest instead?"* Stop here unless the user says to continue. For each active page, collect: `title`, `category`, `tags`, `summary` (frontmatter field), `lifecycle`, any `^[ambiguous]` or `^[inferred]` markers in the body. ## Step 2: Identify Themes From all active pages' tags, tally theme frequency: ``` For each tag across new + updated pages: count how many active pages carry it Sort descending, take top 5 ``` Also read `$OBSIDIAN_VAULT_PATH/_meta/taxonomy.md` (if it exists). Flag any tag from step 1 that **does not appear** in the taxonomy — these are new vocabulary words that emerged this period. Note which categories grew most (concepts/, entities/, skills/, synthesis/, references/, etc.). ## Step 3: Find Notable New Connections Scan new and updated pages for cross-category wikilinks — links that bridge different knowledge layers. These are the most intellectually interesting outputs of the period. For each active page, extract all `[[wikilink]]` targets. Classify each link by the target's category prefix. Flag links that cross categories (e.g., a `concepts/` page linking to an `entities/` page, or a `synthesis/` page bridging two topics). Rank candidates by interestingness: - **+3** if the link is across two categories that rarely connect (use `_insights.md` bridge data if available) - **+2** if the target page is a top-10 hub (per `_insights.md` anchors) - **+2