CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

wiki-narrate

Turn a wiki topic into a cited Markdown briefing, plain-language explanation, or progressive lecture. Use this skill for topic-based briefing, explanation, and lecture requests that must stay within the evidence compiled in an Obsidian vault.

Quality

85%

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

81%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 tight, high-quality instruction-only skill: fully executable commands, an enumerated failure matrix, and correct offloading of voice skeletons to a real bundle reference. The main improvement levers are consolidating the repeatedly restated write-guard constraints and specifying the readout slug derivation.

Suggestions

Consolidate the hot.md / _readouts/ / index.md do-not-touch rules into a single 'Write Guards' section instead of restating them across Retrieval, Persistence, Logging, and Safe Failure.

Specify the deterministic slug rule (e.g., lowercase topic, spaces to hyphens, stripped of path characters) so the _readouts/<slug>.md filename is unambiguous.

Clarify where llm-wiki/SKILL.md, WRITING.md, and the Config Resolution Protocol live, or inline the minimal needed details, so the skill is self-contained when the sibling bundle is not present.

DimensionReasoningScore

Conciseness

The body is dense and prescriptive with no concept-explanation padding, but the hot.md/_readouts_/index.md do-not-touch constraints are restated across the Retrieval, Persistence, Logging, and Safe Failure sections and could be consolidated. Not 3 because every other token is load-bearing; not 5 because the repetition is a real trimming opportunity.

4 / 5

Actionability

Concrete throughout: exact command syntax, a copy-paste-ready log command with all flags, explicit exclusion lists, marker syntax (^[inferred], ^[ambiguous]), and saved-readout frontmatter fields. Minor gaps keep it from 5: the <slug> is described as deterministic and filesystem-safe but never specified, and external dependencies (llm-wiki/SKILL.md, Config Resolution Protocol) cannot be resolved from this bundle.

4 / 5

Workflow Clarity

The flow (contract → retrieval → ledger → draft → persist → log) is clearly sequenced, and the Safe Failure Behavior section enumerates explicit error-recovery paths for no-match, weak evidence, QMD fallback, write failure, and log failure — feedback loops and validation checkpoints are fully present.

5 / 5

Progressive Disclosure

Voice skeletons are appropriately split into references/voices.md, which exists in the bundle and is clearly signaled one level deep (verified). Not 5 because several referenced resources (llm-wiki/SKILL.md, WRITING.md, AGENTS.md, .manifest.json) live outside this bundle and are not navigable or verifiable from it.

4 / 5

Total

17

/

20

Passed

Description

83%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: it states concrete capabilities in third person, gives an explicit "Use this skill for..." trigger clause, and carves out a distinct niche (cited narration confined to Obsidian vault evidence). The only weaknesses are a few missing natural synonyms and a slightly narrow trigger vocabulary.

DimensionReasoningScore

Specificity

"Turn a wiki topic into a cited Markdown briefing, plain-language explanation, or progressive lecture" names the domain and several concrete output actions, but coverage stops short of the comprehensive multi-action list of the 5 anchor (retrieval, persistence, and voices are absent).

4 / 5

Completeness

The description explicitly answers both what ("Turn a wiki topic into a cited Markdown briefing, plain-language explanation, or progressive lecture") and when ("Use this skill for topic-based briefing, explanation, and lecture requests that must stay within the evidence compiled in an Obsidian vault") with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Natural trigger terms like "briefing", "explanation", "lecture", "topic", and "Obsidian vault" are present and would plausibly appear in user requests, but common synonyms such as "summarize", "readout", or "narrate" are missing. Not 3 because the existing keyword set is genuinely natural rather than generic.

4 / 5

Distinctiveness Conflict Risk

The vault-evidence constraint gives the skill a clear, distinct niche with minimal conflict risk, but the broad term "explanation" could overlap generic explain-request skills, keeping it just below the 5 anchor.

4 / 5

Total

17

/

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

Ar9av/obsidian-wiki

Path

.skills/wiki-narrate/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.