CtrlK
BlogDocsLog inGet started
Tessl Logo

plannotator-last

Open Plannotator on the latest rendered assistant message and use the returned annotations to revise that message or continue.

66

Quality

78%

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

Fix and improve this skill with Tessl

tessl review fix ./apps/skills/core/plannotator-last/SKILL.md
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 content is a model short skill: lean, copy-paste actionable, with a clear sequenced workflow that branches on every outcome and no padding or over-explanation.

DimensionReasoningScore

Conciseness

The body is lean: it never explains what Plannotator or annotations are, and every line — the preamble warning, the command, the behavior list, and the closing guidance — earns its place, matching 'Lean and efficient; assumes Claude's competence; every token earns its place'.

5 / 5

Actionability

It gives a copy-paste command ('plannotator last') and explicitly handles every common outcome (feedback returned, no feedback, approval carrying notes), so the guidance is fully actionable; absence of code is not penalized for this instruction-only skill.

5 / 5

Workflow Clarity

A clear numbered sequence with a 'Wait for the annotation session to finish' checkpoint and branching for each outcome; as a simple single-command skill it qualifies for the simple-skill exception, and there is no destructive/batch operation to trigger the validation cap.

5 / 5

Progressive Disclosure

At well under 50 lines with no need for external references, the body is organized into clear sections (intro, warning, command, behavior, closing), satisfying the simple-skill exception for progressive disclosure.

5 / 5

Total

20

/

20

Passed

Description

57%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 specific and clearly distinct, but it omits any 'Use when...' trigger guidance and relies on only a couple of domain keywords, which caps completeness and trigger-term quality at the midpoint.

Suggestions

Add an explicit 'Use when...' clause to the description, e.g. 'Use when the user wants to annotate or get feedback on your last response via Plannotator.', so the 'when' is answered in the frontmatter.

Broaden trigger-term coverage with natural user phrases and synonyms such as 'annotate', 'review', 'feedback on', and 'last response' alongside 'Plannotator' and 'annotations'.

Consider adding one more concrete outcome (e.g. 'approve or request changes') to lift specificity from 1-2 actions toward several.

DimensionReasoningScore

Specificity

Names the domain ('Plannotator', 'latest rendered assistant message', 'annotations') and two concrete actions ('Open Plannotator...', 'use the returned annotations to revise that message or continue'), matching the '1-2 concrete actions, but not comprehensive' anchor rather than 4 which requires several actions.

3 / 5

Completeness

It clearly states what the skill does, but there is no 'Use when...' clause or equivalent trigger guidance in the description (that guidance lives only in the body), so per the judging guideline completeness is capped at 3 — a clear 'what' with 'when' missing.

3 / 5

Trigger Term Quality

The only natural keywords are 'Plannotator' and 'annotations' — relevant to the domain but with no synonyms, variations, or natural user phrasing, fitting 'Some relevant keywords but missing common variations or synonyms' rather than 4's broader coverage.

3 / 5

Distinctiveness Conflict Risk

'Open Plannotator on the latest rendered assistant message' names a specific product and a narrow target (the latest assistant response), giving it a clear niche with minimal overlap risk, matching the score 5 anchor.

5 / 5

Total

14

/

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.