CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

84%

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

The canonical home for this skill is obsidian-clipper-template-creator in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

85%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 well-structured instruction-only skill: the workflow is clearly sequenced with explicit selector-verification checkpoints and error-recovery feedback loops, and content is appropriately split across six real, one-level-deep reference files. The only weaknesses are minor — a duplicated reference link, some redundancy between step 3 and the verification rules section, and a stubbed inline JSON example.

DimensionReasoningScore

Conciseness

The body is efficient with no explanations of concepts Claude already knows, but has minor trims available: [references/analysis-workflow.md] is linked twice in step 3, and the selector-verification rules in step 3's actions are restated nearly verbatim in the separate "Selector Verification Rules" section ("Never guess selectors" appears in both). This matches the level-4 anchor ("Efficient; minor instances of over-explanation that could be trimmed") rather than level 5's every-token-earns-its-place.

4 / 5

Actionability

Guidance is concrete and executable throughout: "Read `Bases/*.base` to find a matching category", "Use **WebFetch** to retrieve page content", "Analyze the HTML for Schema.org JSON, Meta tags, and CSS selectors", with fallbacks (browser DOM snapshot, ask for another URL). The minor gap is the inline JSON example, which is a stub ending in "..." rather than a complete copy-paste-ready template, deferring instead to references and assets — level 4 ("Mostly executable guidance; concrete code or commands with minor gaps"), not level 5's fully executable examples.

4 / 5

Workflow Clarity

The six-step workflow is clearly sequenced (identify intent → check Bases → fetch and analyze → draft JSON → consider logic → verify variables) with explicit validation checkpoints ("Verify each selector against the fetched content. Do not guess selectors") and genuine feedback loops for error recovery ("If a selector cannot be verified from the fetched content, state that explicitly and ask for another URL", plus a dedicated Selector Verification Rules section). This matches the level-5 anchor ("Clear sequence with explicit validation steps; feedback loops for error recovery"); template creation is not a destructive or batch operation, so no cap applies.

5 / 5

Progressive Disclosure

SKILL.md is a lean overview with every topic split into one of six verified reference files (variables, filters, json-schema, logic, bases-workflow, analysis-workflow, each 44-79 lines) plus two example assets, all existing on disk and cross-linked only as siblings — no nested chains. All references are clearly signaled both inline at the relevant workflow step and in the Resources section with one-line descriptions, matching the level-5 anchor ("Clear overview with well-signaled one-level-deep references; content appropriately split; easy navigation").

5 / 5

Total

18

/

20

Passed

Description

78%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 well-crafted description that explicitly states both what the skill does and when to use it, with domain-specific trigger terms that make it highly distinguishable. The main weakness is that the 'what' is a single generic action ("creating templates") with no mention of the importable JSON output or Bases integration, leaving minor coverage gaps.

Suggestions

Expand the 'what' portion with concrete capabilities, e.g. "Create importable JSON clipping templates for the Obsidian Web Clipper, map them to Base schemas, and verify selectors against live pages."

Add natural trigger synonyms users might say, such as "clip web pages", "save articles to Obsidian", or "web clipper template".

DimensionReasoningScore

Specificity

The description lists several concrete actions — "create a new clipping template", "understand available variables", "format clipped content" — anchored to the Obsidian Web Clipper domain, but coverage has minor gaps (no mention of importable JSON output, Bases mapping, or selector verification). This matches the level-4 anchor ("Lists several specific actions; minor gaps in coverage") better than level 3 (only 1-2 actions) or level 5 (comprehensive coverage).

4 / 5

Completeness

Both parts are explicit: the 'what' is "Guide for creating templates for the Obsidian Web Clipper" and the 'when' is a clear "Use when you want to create a new clipping template, understand available variables, or format clipped content" clause. It falls short of the level-5 anchor because the 'what' is a single generic action rather than multiple concrete capabilities, placing it at level 4 ("both present; could be more explicit or specific") and clearly above level 3 (weak/missing 'when').

4 / 5

Trigger Term Quality

Natural trigger terms are present — "Obsidian Web Clipper", "clipping template", "variables", "format clipped content" — giving good keyword coverage, but common variations like "clip a webpage", "save web pages to Obsidian", or the .json import extension are missing. This fits the level-4 anchor ("Good keyword coverage; a few natural terms missing") rather than level 5's comprehensive synonyms/extensions.

4 / 5

Distinctiveness Conflict Risk

The description occupies a clear niche (Obsidian Web Clipper templates) with distinct triggers like "clipping template" that no other generic skill would claim, matching the level-5 anchor ("Clear niche with distinct triggers; minimal conflict risk"). At worst a general Obsidian note-taking skill overlaps slightly, which would be level 4, but the Clipper-specific trigger terms keep conflict risk minimal.

5 / 5

Total

17

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

plugins/AI-Agents-Safe-Coding-Skills/skills/obsidian-clipper-template-creator/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.