wiki-digest
Generate a periodic knowledge digest — a human-readable newsletter-style summary of what was learned, updated, and connected in your wiki over a specified period (day/week/month). Use when the user says "what did I learn this week", "give me a digest", "weekly summary", "knowledge report", "what's new in my wiki", "/wiki-digest [period]", "summarize my recent learning", or wants a readable overview of recent wiki activity. Distinct from wiki-status (which reports ingestion delta of sources) — wiki-digest summarizes *knowledge*, not sources.
Ar9av · 已有 AI 审核记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add Ar9av/obsidian-wiki --skill wiki-digest技能说明
name: wiki-digest description: > Generate a periodic knowledge digest — a human-readable newsletter-style summary of what was learned, updated, and connected in your wiki over a specified period (day/week/month). Use when the user says "what did I learn this week", "give me a digest", "weekly summary", "knowledge report", "what's new in my wiki", "/wiki-digest [period]", "summarize my recent learning", or wants a readable overview of recent wiki activity. Distinct from wiki-status (which reports ingestion delta of sources) — wiki-digest summarizes knowledge, not sources.
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
Writing profile: Before drafting or rewriting natural-language Markdown, read and apply the Writing Profile Resolution section in llm-wiki/SKILL.md. Framework schema, provenance, safety, and operation-specific requirements take precedence.
WRITING.md preferences apply only to newly drafted or rewritten natural-language Markdown; preserve source content and structured records.
- Resolve config — follow the Config Resolution Protocol in
llm-wiki/SKILL.md(inline@nameoverride → walk up CWD for.env→ global config → prompt setup). This givesOBSIDIAN_VAULT_PATHandOBSIDIAN_LINK_FORMAT. - 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
- Read
$OBSIDIAN_VAULT_PATH/log.md— last 200 lines — for entries within the period (timestamps are ISO-8601 prefixed lines). - Read
$OBSIDIAN_VAULT_PATH/hot.mdfor current session context. - If
$OBSIDIAN_VAULT_PATH/_insights.mdexists, 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 writtenupdated— when it was last modified
Classify:
- New pages:
createdis within the period - Updated pages:
updatedis within the period butcreatedis 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.mdbridge data if available) - +2 if the target page is a top-10 hub (per
_insights.mdanchors) - +2 if the link appears in a
synthesis/page (deliberate cross-cutting) - +1 if the source page is marked
^[inferred](synthesized connection, not directly stated)
Take the top 3–5 connections. Write each as a plain-English sentence: not just "A → B" but why the connection is interesting.
Step 4: Surface Open Threads
Scan active pages and _raw/ for unresolved work:
- Drafts: pages with
lifecycle: draftorlifecycle: stub - Ambiguous claims: count
^[ambiguous]markers across all active pages (don't list every one — just the count and which pages have the most) - Unstaged notes: count files in
$OBSIDIAN_VAULT_PATH/_raw/(anything here hasn't been promoted) - Taxonomy gaps: tags from Step 2 that aren't in
_meta/taxonomy.md
Step 5: Choose Recommended Re-reads
From the existing (pre-period) pages, identify 2–3 worth revisiting given this week's new context.
Heuristic: find pre-period pages that share the most tags with the active pages from Step 1. These are foundational pages whose topic was extended this period — the new pages build on them but the user may not have revisited the foundation.
Also include any pre-period page that now has 2+ new incoming links from active pages (it just became more connected — a sign it's load-bearing).
Write each recommendation with a concrete reason: "[[concepts/attention-mechanism]] — your foundational page; three new papers ingested this week all extend it", not just the page title.
Step 6: Generate the Digest
Produce a structured, scannable markdown report. The Headlines secti
阅读完整来源 ↗