CtrlK
BlogDocsLog inGet started
Tessl Logo

plannotator-annotate

Open Plannotator's annotation UI for a markdown file, plain-text config file (.yaml, .json, .toml, .ini, .csv, .log, …), HTML file, URL, or folder and then respond to the returned annotations.

67

Quality

80%

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

Fix and improve this skill with Tessl

tessl review fix ./apps/skills/core/plannotator-annotate/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

93%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, actionable, well-structured single-purpose skill with copy-paste commands and clear outcome handling. The only minor gap is the absence of explicit validation checkpoints, which are not strictly necessary for this non-destructive annotation workflow.

DimensionReasoningScore

Conciseness

Lean and efficient with no padding or explanation of concepts Claude already knows; every line (the approve-button caveat, the --json clarification) earns its place.

5 / 5

Actionability

Provides copy-paste-ready, fully executable commands for both the ordinary and --gate --json cases, covering the common scenarios.

5 / 5

Workflow Clarity

The numbered Behavior list gives a clear sequence with outcome branching and an error-recovery loop (step 6 re-runs on unresolved args), but there are no explicit validation checkpoints; acceptable for this non-destructive task, hence just above midpoint.

4 / 5

Progressive Disclosure

Under 50 lines, single-purpose, no external references or bundle files needed; content is well-organized with clear headers, code blocks, and a numbered list, which qualifies for 5 per the simple-skills guidance.

5 / 5

Total

19

/

20

Passed

Description

66%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 is concrete and well-targeted with good keyword and extension coverage, but it lacks an explicit 'when to use' trigger clause, which caps its completeness. Adding a 'Use when...' sentence referencing natural user phrases (annotate, review, approve) would raise it.

Suggestions

Add an explicit 'Use when...' clause with natural trigger phrases such as 'annotate', 'review', 'give feedback on', or 'approve' a document.

Include user-facing synonyms like 'review' and 'feedback' alongside 'annotation' to broaden trigger-term coverage.

Clarify the approval/gate trigger explicitly in the description so users know when to expect approval vs feedback.

DimensionReasoningScore

Specificity

Names a concrete action ('Open Plannotator's annotation UI', 'respond to the returned annotations') and comprehensively enumerates target types (markdown, config files with extensions, HTML, URL, folder); only two core actions, so just shy of a 5.

4 / 5

Completeness

The 'what' is clear (open annotation UI and respond to annotations), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric.

3 / 5

Trigger Term Quality

Good keyword coverage including file extensions (.yaml, .json, .toml, .ini, .csv, .log) and 'annotation', but missing common natural phrases a user might say such as 'review', 'feedback', or 'approve'.

4 / 5

Distinctiveness Conflict Risk

The 'Plannotator' product name gives it a clear niche with minimal conflict risk, though the broad target list (markdown, config, HTML, URL, folder) leaves minor overlap with general document skills.

4 / 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.

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.