CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

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

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

92%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.

An exceptionally tight, prescriptive skill body with executable command, citation, persistence, and logging contracts plus thorough safe-failure handling. The only blemish is mild redundancy of invariants across the failure sections.

DimensionReasoningScore

Conciseness

The body is dense and prescriptive with no padding about concepts Claude already knows, but failure rules (e.g., hot.md/index.md invariants) are restated across Persistence, Logging, and Safe Failure Behavior, which could be consolidated.

4 / 5

Actionability

Provides copy-paste-ready concrete guidance: exact command syntax, the literal log-event format, specific file paths like '_readouts/<slug>.md', named frontmatter fields, explicit exclusion lists, and canonical voice names.

5 / 5

Workflow Clarity

A clearly sequenced multi-step workflow (Retrieval → Claim Ledger → Drafting → Persistence → Logging) with explicit validation checkpoints and error-recovery feedback loops for write and log failures.

5 / 5

Progressive Disclosure

The overview body is well-organized by section and points to a single one-level-deep, clearly signaled reference ('Read references/voices.md') that exists as a real bundle file; content is appropriately split.

5 / 5

Total

19

/

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, third-person description that clearly states what the skill does and when to use it, with concrete output modes and an explicit trigger clause. It could be sharpened with synonyms/file extensions and tighter distinctiveness around the broad briefing/explanation triggers.

DimensionReasoningScore

Specificity

Names the domain and several concrete output modes — 'cited Markdown briefing, plain-language explanation, or progressive lecture' — but does not enumerate the internal steps (retrieval, citation audit, persistence), leaving minor gaps in coverage.

4 / 5

Completeness

Explicitly answers both what ('Turn a wiki topic into a cited Markdown briefing...') 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 a concrete trigger clause.

5 / 5

Trigger Term Quality

Includes natural terms users would say — 'briefing', 'explanation', 'lecture', 'topic-based' — plus 'Obsidian vault', but lacks synonyms or file-extension variants, so a few natural terms are missing.

4 / 5

Distinctiveness Conflict Risk

The Obsidian-vault-evidence constraint carves a clear niche, but the trigger phrases 'briefing, explanation, and lecture' are broad enough to risk minor overlap with general explanation skills.

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.

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.