CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

plannotator-annotate

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

67

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

SKILL.md
Quality
Evals
Security

Quality

Content

96%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 model of lean, executable instruction writing: an auto-run command followed by an exhaustive, deterministic case analysis of its output, with exact strings to match, exact acknowledgments to give, and a concrete fallback when arguments cannot be resolved. The only flaw is organizational — the '## Markdown annotations' section header undersells the skill's actual scope (HTML, URL, and folder targets).

Suggestions

Rename the '## Markdown annotations' header to something scope-accurate (e.g. '## Start the annotation session'), since the command and output cases handle markdown files, HTML files, URLs, and folders, not just markdown.

DimensionReasoningScore

Conciseness

Every sentence carries non-obvious operational detail — exact output strings ('The exact text `The user approved.`'), JSON decision values ('"decision": "approved"'), and exact acknowledgment text ('Approved.'). There is no padding and no explanation of concepts Claude already knows.

5 / 5

Actionability

Fully executable: a copy-paste-ready command ('plannotator annotate $ARGUMENTS'), exact strings to match on, exact responses to give for each case, and a concrete recovery step in case 4 (re-run 'plannotator annotate <path-or-url>' keeping any echoed flags). All four output cases have specific handling instructions.

5 / 5

Workflow Clarity

A simple single-purpose skill whose single action is unambiguous: run one command, then branch deterministically across four enumerated output cases, each with an explicit termination condition ('acknowledge with a single sentence ... and stop') or follow-on instruction. Case 4 even closes the loop by re-handling per cases 1-3, and no destructive or batch operations are involved so the validation cap does not apply.

5 / 5

Progressive Disclosure

A 20-line body with clear sections and no external references needed, which would normally merit 5 under the simple-skill exception, but the header '## Markdown annotations' mislabels scope — the command and cases cover HTML files, URLs, and folders too, so a reader scanning headers would underestimate coverage. This minor organization gap fits 'minor organization gaps' at level 4 better than the well-organized-slices level 5.

4 / 5

Total

19

/

20

Passed

Description

65%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 states a clear, distinctive 'what' — opening Plannotator's annotation UI for markdown files, HTML files, URLs, or folders and responding to returned annotations — but it omits any 'when to use' guidance and describes only two actions, one of which ('respond to the returned annotations') is generic. Since the skill sets disable-model-invocation: true and is user-invoked, the missing trigger clause matters less in practice, but as written the rubric's completeness cap applies.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user wants to review or annotate a markdown file, HTML file, URL, or folder with inline comments' — the missing 'when' currently caps completeness at 3.

Make the second action concrete: replace 'respond to the returned annotations' with what responding involves (addressing annotation feedback vs. acknowledging approval) to lift specificity.

Include natural synonyms and file extensions among trigger terms ('.md', '.html', 'review', 'comment on') to move trigger-term quality toward comprehensive.

DimensionReasoningScore

Specificity

It names the domain (Plannotator annotation) and two actions — 'Open Plannotator's annotation UI' and 'respond to the returned annotations' — plus an enumeration of target types (markdown file, HTML file, URL, or folder). This matches 'names domain and 1-2 concrete actions, but not comprehensive': the second action is generic about what responding entails, and level 4 requires 'several specific actions', which two does not reach.

3 / 5

Completeness

It has a clear 'what' (open the annotation UI for four target types, then respond to returned annotations) but no 'when' — there is no 'Use when...' clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 3. Level 4 requires both, and the 'when' is entirely absent rather than merely imprecise.

3 / 5

Trigger Term Quality

Good natural keyword coverage: 'annotation', 'markdown file', 'HTML file', 'URL', 'folder', and the tool name 'Plannotator'. Missing common variations — file extensions (.md, .html) and synonyms such as 'review' or 'comment' — so it falls short of level 5's 'including synonyms and file extensions' but sits above level 3's sparse keyword set.

4 / 5

Distinctiveness Conflict Risk

'Plannotator's annotation UI' pins the skill to a specific named tool with distinct triggers tied to concrete target types, giving it a clear niche with minimal conflict risk against other skills.

5 / 5

Total

15

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

backnotprop/plannotator

Path

apps/skills/claude/plannotator-annotate/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.