obsidian-literature-workflow

Use this skill for project-scoped literature review built on Sources/Papers, with synthesis landing in Knowledge, writing handoff in Writing, and the default literature canvas under Maps/literature.canvas.

Quality

73%

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-literature-workflow/SKILL.md

Quality

Content

72%

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

A lean, well-organized overview with excellent progressive disclosure and verified references, but the body defers execution detail to references and only names its validation gate without a recovery loop.

Suggestions

Add a short worked example or inline the key procedure (e.g. one paper flowing through extraction to a promoted claim) so the body is executable without immediately jumping to references.

Spell out evidence-gate failure handling as an explicit validate->fix->retry loop (e.g. 'If a claim lacks the required fields, do not promote it; revise the note and re-check before any Writing handoff').

Dimension	Reasoning	Score
Conciseness	The body is lean (~40 lines) with no concept over-explanation or padding; every section (flow, outputs, rules, read-next) earns its place and assumes Claude's competence.	3 / 3
Actionability	It gives concrete output paths and a specific ruleset (e.g. promoted claims must carry 'Evidence Record ID, source type, claim strength, allowed wording, and forbidden stronger wording'), but the actual procedures for extracting claims and building the canvas are deferred to references, leaving the body incomplete for execution on its own.	2 / 3
Workflow Clarity	The pipeline diagram ('Sources/Papers/ -> Knowledge/ -> Writing/ -> Maps/literature.canvas') gives a clear sequence and the 'evidence gate' is an explicit checkpoint, but the body lacks a validate->fix->retry feedback loop and step-level detail for what happens when a claim fails promotion.	2 / 3
Progressive Disclosure	It is a concise overview with a well-signaled 'Read next' section listing six one-level-deep references, all of which exist in ./references/, giving easy navigation without nested lookups.	3 / 3
	Total	10 / 12 Passed

Description

75%

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 specific, well-scoped description with an explicit trigger and a distinctive vault structure, though it leans on structural destinations over concrete action verbs and natural trigger variations.

Suggestions

Add natural trigger phrasings users would actually say, e.g. 'Use when the user asks for a literature review, paper review, research synthesis, or annotated bibliography in an Obsidian vault'.

Replace some structural destinations with concrete action verbs (e.g. 'extract claims, synthesize research gaps, and promote evidence-backed claims into writing') to raise specificity.

Dimension	Reasoning	Score
Specificity	Names the domain and concrete destinations ('built on Sources/Papers', 'synthesis landing in Knowledge', 'writing handoff in Writing', 'literature canvas under Maps/literature.canvas'), but it describes pipeline structure and locations rather than enumerating discrete action verbs, so it stops short of the 'multiple specific concrete actions' anchor.	2 / 3
Completeness	It opens with an explicit trigger clause ('Use this skill for project-scoped literature review...') and clearly states what the skill does across the pipeline, satisfying both the 'what' and an explicit 'when' trigger.	3 / 3
Trigger Term Quality	It includes relevant terms ('project-scoped literature review', 'synthesis', 'literature canvas') but leans on vault-specific folder names rather than natural variations a user would say, missing common phrasings like 'paper review', 'research synthesis', or 'annotated bibliography'.	2 / 3
Distinctiveness Conflict Risk	The specific Obsidian vault layout (Sources/Papers -> Knowledge -> Writing -> Maps/literature.canvas) carves a clear niche, making it unlikely to trigger for unrelated skills.	3 / 3
	Total	10 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: Galaxy-Dawn/claude-scholar
Path: skills/obsidian-literature-workflow/SKILL.md
Commit: 2f7766f

Reviewed: about 13 hours 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.