CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

72

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

82%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A thorough, well-structured instruction skill with concrete heuristics, a complete output template, and strong error-handling guidance via the Edge Cases table. It is slightly held back by light redundancy between the template and Notes, and by the absence of an explicit final-output validation step.

Suggestions

Add an explicit verification checkpoint before output (e.g., confirm every table row maps to a scanned page and every Headline is a synthesized insight, not a page title) to push workflow_clarity toward 5.

Trim redundancy between the report template and the Notes section — the 'Headlines are the payoff' and 'Be concrete about re-reads' notes already follow from the template annotations.

Consider extracting the full report template or the QMD Refresh section into a reference file so the main SKILL.md reads as a tighter overview, improving progressive_disclosure.

DimensionReasoningScore

Conciseness

Mostly lean and assumes Claude's competence (no primers on wikis, tags, or frontmatter), but the full report template and the Notes section restate guidance already embedded in the steps, leaving minor trim opportunities; not a 5 because of that light redundancy.

4 / 5

Actionability

Highly concrete and executable: exact frontmatter fields to read (created/updated), specific scoring heuristics (+3/+2/+2/+1), exact file paths ($OBSIDIAN_VAULT_PATH/log.md, _insights.md), a complete output template, and copy-paste QMD commands (${QMD_CLI:-qmd} update / embed / ls / get).

5 / 5

Workflow Clarity

Clear sequenced workflow (Before You Start → Steps 1–7) with an explicit gate ("If fewer than 5 pages were active... Stop here unless the user says to continue") and an Edge Cases table for recovery, but the main digest generation lacks an explicit verify-the-output checkpoint, so it sits below the 5-anchor.

4 / 5

Progressive Disclosure

Well-organized with clear section headers and a well-signaled one-level reference ("follow the Config Resolution Protocol in `llm-wiki/SKILL.md`") with no nested references; not a 5 because no bundle files exist and the lengthy inline report template plus the tangential QMD Refresh section could arguably live in separate reference files.

4 / 5

Total

17

/

20

Passed

Description

95%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description that clearly states what the skill produces, when to invoke it via numerous natural triggers, and how it differs from the related wiki-status skill. The only minor gap is that it describes one composite output rather than multiple discrete actions.

DimensionReasoningScore

Specificity

Names the domain and several concrete facets — "summary of what was learned, updated, and connected" over "a specified period (day/week/month)" — but it is essentially one product (a digest) rather than a list of distinct operations, so it falls just below the comprehensive 5-anchor.

4 / 5

Completeness

Explicitly answers both what ("Generate a periodic knowledge digest — a human-readable newsletter-style summary...") and when ("Use when the user says...") with concrete trigger phrases, matching the 5-anchor exactly.

5 / 5

Trigger Term Quality

Comprehensive natural trigger coverage including synonyms and the slash command: "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".

5 / 5

Distinctiveness Conflict Risk

Explicitly carves a niche from a sibling skill — "Distinct from wiki-status (which reports ingestion delta of sources) — wiki-digest summarizes *knowledge*, not sources" — giving clear triggers and minimal conflict risk.

5 / 5

Total

19

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
Ar9av/obsidian-wiki
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.