obsidian-kb-artifacts

Use this skill for Obsidian-native formatting and derived artifacts such as Markdown formatting, wikilinks, registry tables, canvas files, optional Bases, CLI operations, and link repair. This skill does not decide knowledge routing.

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/obsidian-kb-artifacts/SKILL.md

Quality

Content

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

The body is concise and well-structured with verified one-level-deep references, but it provides no executable guidance — only high-level responsibilities and rules, leaving Claude without concrete steps or commands. Pushing actionable detail into the references is acceptable for progressive disclosure, but the SKILL.md itself offers no anchor of actionability.

Suggestions

Add at least one concrete executable example per core responsibility (e.g., a sample CLI command or a wikilink/canvas snippet) so the body gives actionable guidance rather than only listing tasks.

Reference the most-used reference inline with a one-line pointer for the primary task (e.g., 'For canvas generation, see CANVAS.md') to give Claude an immediate entry point.

Include a brief worked example of link repair or registry-table formatting directly in the body to lift actionability above the abstract listing level.

Dimension	Reasoning	Score
Conciseness	The body is a lean overview of responsibilities and rules with no padding or explanation of concepts Claude already knows; every line earns its place, matching the 'lean and efficient' anchor.	5 / 5
Actionability	The body only describes responsibilities and rules ('Obsidian Markdown formatting', 'link repair should strengthen existing canonical notes') with no concrete code, commands, or executable steps, matching the 'entirely vague or abstract; no concrete code' anchor.	1 / 5
Workflow Clarity	There is no multi-step workflow in the body, but the skill is single-purpose/format-oriented and its single action is unambiguous, so per the simple-skill exception workflow clarity reaches 5; there is no destructive/batch sequence present to require validation checkpoints.	5 / 5
Progressive Disclosure	The body is a clear overview with a 'Read next' section signaling six one-level-deep references (OBSIDIAN-MARKDOWN, CANVAS, BASES, REGISTRY-TABLES, LINK-REPAIR, CLI), all verified to exist in ./references/, matching the 'clear overview with well-signaled one-level-deep references' anchor.	5 / 5
	Total	16 / 20 Passed

Description

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

The description is specific, covers a clear niche, and explicitly states both what it does and when to use it, with a useful negative-scope boundary. Minor gaps in synonym/extension trigger coverage keep specificity and trigger-term quality just below 5.

Dimension	Reasoning	Score
Specificity	Lists several specific concrete actions (Markdown formatting, wikilinks, registry tables, canvas files, optional Bases, CLI operations, link repair) with only minor coverage gaps, matching the 'several specific actions; minor gaps' anchor rather than the comprehensive 5.	4 / 5
Completeness	Explicitly answers both 'what' (formatting and derived artifacts enumerated) and 'when' ('Use this skill for...'), with a concrete negative-scope trigger ('does not decide knowledge routing'), matching the 'clearly and explicitly answers both' anchor.	5 / 5
Trigger Term Quality	Good keyword coverage including natural terms users say (wikilinks, canvas files, link repair) plus file-type cues (.base, Maps/), but missing common synonyms/extensions a user might say, so not a 5.	4 / 5
Distinctiveness Conflict Risk	The narrow Obsidian-native formatting niche plus an explicit conflict-avoidance clause ('does not decide knowledge routing') gives a clear niche with minimal overlap, matching the 5 anchor.	5 / 5
	Total	18 / 20 Passed

Validation

100%

Warnings & errors only

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: Galaxy-Dawn/claude-scholar
Path: skills/obsidian-kb-artifacts/SKILL.md
Commit: 6ed46da

Reviewed: 8 days ago

Table of Contents

Discovery Implementation Validation

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.