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.

59

Quality

67%

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/claude/plannotator-last/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

100%Weight 40%Scale 1-3

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 tight, executable single-action skill with clear branching logic and no padding. It fully respects the token budget while remaining unambiguous about what to do for each outcome.

DimensionReasoningScore

Conciseness

The body is extremely lean with no concept explanations or padding; every line instructs, assuming Claude's competence, matching the lean-and-efficient anchor.

3 / 3

Actionability

It leads with an executable command ('plannotator annotate-last $ARGUMENTS') and gives concrete, copy-ready handling for each possible output, matching the fully-executable anchor.

3 / 3

Workflow Clarity

The three-branch conditional is clearly sequenced with explicit per-branch actions and stop instructions; as a simple single-action skill with no destructive/batch step this meets the workflow-clarity bar.

3 / 3

Progressive Disclosure

It is a short, well-sectioned single file with no external references needed, satisfying the under-50-lines simple-skill allowance for a top score.

3 / 3

Total

12

/

12

Passed

Description

35%Weight 40%Scale 1-3

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 concrete actions tied to a specific tool, but lacks any natural-language trigger guidance and leans on internal terminology. It is clear on 'what' but silent on 'when'.

Suggestions

Add an explicit 'Use when...' clause with natural user phrasing (e.g., 'Use when the user wants to mark up or revise your last response').

Replace or supplement the jargon term 'latest rendered assistant message' with language a user would actually say.

Tighten the open-ended 'revise that message or continue' into one or two concrete named actions to lift specificity.

DimensionReasoningScore

Specificity

It names concrete actions ('Open Plannotator on the latest rendered assistant message', 'use the returned annotations to revise that message or continue'), but 'continue' is open-ended and the action set is not comprehensive, so it sits at the named-domain-and-some-actions level rather than a full list of multiple specific actions.

2 / 3

Completeness

It answers 'what' the skill does but provides no explicit 'when' trigger guidance, so per the missing-'Use when...' rule completeness is capped at 2.

2 / 3

Trigger Term Quality

There are no 'Use when...' trigger keywords, and the terms present ('latest rendered assistant message', 'annotations') are internal/technical jargon a user would not naturally say, matching the no-natural-keywords anchor.

1 / 3

Distinctiveness Conflict Risk

Naming the specific tool 'Plannotator' gives it a recognizable niche, but with no explicit triggers it could still overlap with general message-editing skills, matching the somewhat-specific-but-could-overlap anchor.

2 / 3

Total

7

/

12

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.