CtrlK
BlogDocsLog inGet started
Tessl Logo

plannotator-annotate

Open Plannotator's annotation UI for a file, folder, or URL, then address the returned annotations.

60

Quality

70%

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/kiro-cli/skills/plannotator-annotate/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%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 tight, executable single-action skill with a clear run command, precise argument spec, and a recovery branch for failure cases; its only gaps are the absence of a concrete worked example and slightly underspecified recovery reasoning.

DimensionReasoningScore

Conciseness

The body is lean and efficient — a single executable command, a one-line argument spec, and one recovery instruction with no padding or concept explanations Claude already knows, matching the anchor 5.

5 / 5

Actionability

Provides a concrete, copy-paste-ready command and an exact list of accepted argument types with a concrete recovery instruction, but lacks a worked example with a real path, leaving a minor gap versus anchor 5.

4 / 5

Workflow Clarity

The single action is unambiguous with a conditional retry branch for unresolved arguments, giving a clear sequence with a feedback loop; the recovery guidance on how to "work out which target" is slightly underspecified, so it does not reach 5.

4 / 5

Progressive Disclosure

A simple skill under 50 lines with no need for external references, well-organized around the run command and argument spec; per the rubric's simple-skill exception this earns a 5.

5 / 5

Total

18

/

20

Passed

Description

53%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 states what the skill does and names a distinctive tool niche, but it omits an explicit "Use when..." trigger clause and lacks broader keyword coverage, capping the completeness and trigger-term dimensions at 3.

Suggestions

Add an explicit "Use when..." clause naming natural triggers, e.g. "Use when the user wants to annotate a file, folder, or URL with Plannotator."

Broaden trigger terms with synonyms and examples (e.g. "annotate", "review and mark up", "comment on a file", ".md/.yaml/.json files").

List a couple more concrete annotation actions to lift specificity toward comprehensive coverage.

DimensionReasoningScore

Specificity

Names the annotation domain and two concrete actions ("Open Plannotator's annotation UI" and "address the returned annotations") plus target types (file, folder, URL), but coverage is not comprehensive enough for a 4.

3 / 5

Completeness

A clear "what" is present (open the annotation UI and address returned annotations), but there is no explicit "Use when..." trigger clause, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

Relevant keywords like "annotation UI", "file, folder, or URL", and "annotations" appear, but common natural synonyms and file extensions are missing, matching the anchor 3 rather than 4.

3 / 5

Distinctiveness Conflict Risk

The named "Plannotator's annotation UI" niche is mostly distinct with only minor overlap risk, though the generic file/folder/URL targeting keeps it just short of a 5.

4 / 5

Total

13

/

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.