obsidian-clipper-template-creator

Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/obsidian-clipper-template-creator/SKILL.md

Quality

Content

85%Scale 1-5

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

This is a well-structured skill that clearly defines a multi-step workflow for creating Obsidian Web Clipper templates, with strong validation checkpoints and excellent progressive disclosure through well-organized references. Its main weakness is the lack of a complete, executable template example inline—the JSON skeleton is minimal. The content is concise and respects Claude's intelligence while providing enough specificity to be actionable.

Suggestions

Include one complete, copy-paste ready JSON template example inline (e.g., a simple YouTube or article template) rather than only a skeleton with '...' to improve actionability.

Dimension	Reasoning	Score
Conciseness	The content is mostly efficient and avoids explaining concepts Claude already knows. There are minor instances of over-explanation (e.g., the parenthetical examples like '(YouTube)', '(Recipe)' and some redundant action labels), but overall it's well-trimmed and respects token budget.	4 / 5
Actionability	The workflow provides concrete, specific steps with clear actions (use WebFetch, read Base files, analyze HTML for Schema.org JSON, etc.). However, it lacks executable code examples or copy-paste ready commands—the JSON output example is a skeleton rather than a complete template. The guidance is specific but not fully executable.	4 / 5
Workflow Clarity	The workflow is clearly sequenced with numbered steps, explicit validation checkpoints (REQUIRED actions for fetching and verifying selectors), and a feedback loop (if selector cannot be verified, ask for another URL). The Selector Verification Rules section adds explicit validation constraints. This is a well-structured multi-step process with appropriate error recovery.	5 / 5
Progressive Disclosure	The SKILL.md serves as a clear overview with well-signaled, one-level-deep references to specific topics (variables.md, filters.md, json-schema.md, logic.md, bases-workflow.md, analysis-workflow.md). References are contextually placed within workflow steps and also collected in a Resources section. Navigation is easy and content is appropriately split. However, since no bundle files were provided, we cannot verify the referenced files exist, but the structure itself is exemplary.	5 / 5
	Total	18 / 20 Passed

Description

57%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 identifies a clear niche (Obsidian Web Clipper templates) and includes an explicit 'Use when' clause, which is good. However, the capabilities listed are vague and high-level rather than concrete actions, and the trigger terms miss common synonyms users might naturally use. The use of second person ('you want') is a minor style issue.

Suggestions

Add concrete actions like 'define frontmatter properties, configure CSS selectors, set up content filters, map metadata variables' instead of generic phrases like 'understand available variables'.

Expand trigger terms to include natural user phrases such as 'clip article', 'save webpage to Obsidian', 'web clipper template syntax', or 'clipper variables'.

Rewrite in third person voice: 'Guides creation of templates...' instead of 'Use when you want to...'

Dimension	Reasoning	Score
Specificity	The description names the domain (Obsidian Web Clipper templates) but the actions are generic: 'creating templates', 'understand available variables', 'format clipped content'. These are vague and don't describe concrete operations like 'define frontmatter mappings', 'configure selectors', or 'set up filters'.	2 / 5
Completeness	The description answers both 'what' (guide for creating templates for Obsidian Web Clipper) and 'when' ('Use when you want to create a new clipping template, understand available variables, or format clipped content'). However, the 'when' clause uses second person ('you want') and the triggers could be more specific with concrete user phrases.	4 / 5
Trigger Term Quality	Includes relevant terms like 'Obsidian Web Clipper', 'clipping template', 'variables', and 'clipped content'. However, it misses natural synonyms and related terms users might say such as 'web scraping', 'bookmark', 'save webpage', 'clip article', or 'note template'.	3 / 5
Distinctiveness Conflict Risk	The description is fairly distinct due to the specific mention of 'Obsidian Web Clipper' which is a niche tool. There could be minor overlap with general Obsidian template skills or web clipping skills, but the combination is reasonably unique.	4 / 5
	Total	13 / 20 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

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

	Total	10 / 11 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: skills/obsidian-clipper-template-creator/SKILL.md
Commit: 57c135b

Reviewed: 3 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.