CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

wiki-synthesize

Systematically discover synthesis opportunities across the Obsidian wiki — pairs or clusters of concepts that co-occur frequently across pages but have no synthesis page connecting them. Creates new synthesis/ pages that draw explicit cross-cutting conclusions. Use when the user says "synthesize my wiki", "create synthesis pages", "what concepts keep coming up together", "/wiki-synthesize", or after a large ingest when the vault has grown significantly.

Quality

90%

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 highly actionable, well-sequenced workflow skill: concrete commands, an explicit scoring rubric, a complete page template, and a verification checklist. The main weaknesses are minor — a few trimmable rationale sentences, no integrated fix-and-retry loop for the batch page-creation step, and the large template inlined rather than split into a reference file.

Suggestions

Trim rationale sentences (e.g., "This gives the user visibility into what the wiki thinks is worth exploring without forcing every synthesis in one run") and consolidate the Tips that repeat the template's italic guidance to tighten conciseness.

Add a mid-workflow validation checkpoint after Step 5 — e.g., re-check the Quality Checklist items per page and fix before moving to the next candidate — to create an explicit fix-and-retry loop for the batch creation step.

Move the ~40-line synthesis page template to a reference file (e.g., references/synthesis-template.md) and link to it from Step 4 to reduce SKILL.md body size and improve progressive disclosure.

DimensionReasoningScore

Conciseness

The body is lean and wiki-specific with no generic explanation of concepts Claude already knows, but a few rationale sentences ("This gives the user visibility into what the wiki thinks is worth exploring...") and slight repetition between the template's italic guidance and the Tips section could be trimmed — matching "efficient; minor instances of over-explanation" rather than every-token-earns-its-place.

4 / 5

Actionability

Fully executable throughout: an exact grep command for backlink discovery, a point-based scoring table with thresholds, a complete copy-paste synthesis page template including frontmatter and provenance fields, and exact log/back-link output formats — covering the common cases concretely.

5 / 5

Workflow Clarity

Seven clearly sequenced steps with prerequisites ("Before You Start") and a terminal Quality Checklist provide validation for this batch operation (so the batch cap does not apply), but there is no explicit fix-and-retry feedback loop integrated between steps — matching "clear sequence with most checkpoints; minor validation gaps" rather than anchor 5's error-recovery loops.

4 / 5

Progressive Disclosure

Well-organized with clear section headers and no unnecessary nesting, but at ~155 lines with the ~40-line page template fully inlined and no bundle/reference split, the template is a candidate for a separate reference file — matching "good structure; most content appropriately placed; minor organization gaps" rather than anchor 5's appropriately split content.

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 and explicitly states both what the skill does and when to use it, with five natural, varied trigger phrases including a slash command and a contextual condition. The only gap is that it captures the two core actions (discover co-occurring pairs, create synthesis pages) but not the supporting workflow steps.

DimensionReasoningScore

Specificity

Names the domain and gives concrete, mechanism-level actions — "discover synthesis opportunities... pairs or clusters of concepts that co-occur frequently across pages but have no synthesis page connecting them" and "Creates new synthesis/ pages that draw explicit cross-cutting conclusions" — but omits parts of the workflow (scoring candidates, back-linking, updating index/log), matching "several specific actions; minor gaps" rather than comprehensive coverage.

4 / 5

Completeness

Explicitly answers both questions: the "what" ("Systematically discover synthesis opportunities... Creates new synthesis/ pages that draw explicit cross-cutting conclusions") and the "when" ("Use when the user says...") with concrete trigger phrases, matching the anchor exactly.

5 / 5

Trigger Term Quality

Covers five natural trigger phrasings users would actually say — "synthesize my wiki", "create synthesis pages", "what concepts keep coming up together", "/wiki-synthesize", plus the contextual "after a large ingest when the vault has grown significantly" — giving comprehensive, synonym-level coverage for this domain.

5 / 5

Distinctiveness Conflict Risk

Clear niche — Obsidian wiki synthesis discovery — with triggers ("synthesize my wiki", "create synthesis pages") that are specific to synthesis and would not naturally fire for ingest or status skills in the same family; 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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

saski/arnesto

Path

.agents/skills/wiki-synthesize/SKILL.md

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.