CtrlK
BlogDocsLog inGet started
Tessl Logo

plannotator-annotate

Open Plannotator's annotation UI for a markdown file, HTML file, URL, or folder and then respond to the returned annotations.

69

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

100%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 a lean, fully executable decision tree with precise match conditions and explicit stop points; it earns top marks across all dimensions as a well-organized single-purpose skill.

DimensionReasoningScore

Conciseness

Lean and efficient with no padding or explanation of concepts Claude already knows; every clause in the decision tree carries actionable information, matching anchor 5.

5 / 5

Actionability

Provides the exact invocation command and a fully executable, copy-paste-ready decision tree with precise string and JSON literals to match and exact responses to emit for each case, matching anchor 5.

5 / 5

Workflow Clarity

Clear single-purpose sequence (invoke tool, then branch on four enumerated output cases with explicit match conditions and stop points); not a destructive or batch operation, so the validation cap does not apply, and the per-case matching serves as the validation checkpoint, matching anchor 5.

5 / 5

Progressive Disclosure

Under 50 lines with no bundle files needed and well-organized section headers ('Markdown annotations', 'Your task'); per the rubric's simple-skill exception, this qualifies for anchor 5.

5 / 5

Total

20

/

20

Passed

Description

70%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 clearly conveys what the skill does and is highly distinct, but it lacks an explicit 'when to use it' trigger clause, which caps completeness at 3 and limits trigger-term coverage.

Suggestions

Add an explicit 'Use when ...' clause naming the natural trigger phrases (e.g., 'Use when the user wants to annotate, review, or comment on a markdown file, HTML file, URL, or folder').

Include common synonyms and file extensions (e.g., '.md', '.html') alongside the existing target types to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain ('Plnotator's annotation UI') with two concrete actions ('Open ... annotation UI', 'respond to the returned annotations') plus four concrete target types (markdown file, HTML file, URL, folder); falls at anchor 4 rather than 3 due to the concrete target enumeration, but stops short of anchor 5's comprehensive multi-action coverage.

4 / 5

Completeness

Has a clear 'what' (open the annotation UI for the listed targets and respond to returned annotations) but no explicit 'Use when...' trigger clause; per the rubric guideline, a missing explicit trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

Includes natural terms ('annotation', 'annotations', 'markdown file', 'HTML file', 'URL', 'folder') a user might say, but lacks common synonyms and file extensions like '.md' or '.html' that anchor 5 expects; clearly above anchor 3's partial coverage.

4 / 5

Distinctiveness Conflict Risk

Targets a clearly distinct niche ('Plnotator's annotation UI' with specific file/URL/folder inputs) with minimal overlap risk against other skills, matching anchor 5's 'clear niche with distinct triggers'.

5 / 5

Total

16

/

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
backnotprop/plannotator
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.