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.

62

Quality

73%

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-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 an efficient, fully actionable, well-structured simple skill: one executable command and a clear decision tree for its three possible outcomes, with no wasted tokens.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence: a single executable invocation plus a tight enumeration of three outcomes with no padding or explanation of concepts Claude already knows.

5 / 5

Actionability

It gives a copy-paste-ready command (`!`plannotator annotate-last $ARGUMENTS``) and concrete, executable decision rules keyed to exact literal strings ("The user approved.", `"decision": "approved"`).

5 / 5

Workflow Clarity

As a simple single-action skill it sequences the one action and its three branches (approved, dismissed, annotated) with explicit stop/proceed guidance; no destructive or batch step triggers the validation cap.

5 / 5

Progressive Disclosure

Under 50 lines with no external references needed, it is organized into clear labeled sections ("Message annotations", "Your task"), satisfying the simple-skill exception for progressive disclosure.

5 / 5

Total

20

/

20

Passed

Description

46%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 concrete, distinct capability but omits any explicit "Use when..." trigger guidance and relies on technical rather than natural user vocabulary, weakening trigger term quality and completeness.

Suggestions

Add a "Use when..." clause naming natural triggers, e.g. "Use when the user asks to review or annotate your last reply, or says 'check this answer' / 'mark this up'."

Surface more concrete actions to lift specificity, e.g. annotate the last message, surface inline comments, and revise or continue based on feedback.

Include natural user-language keywords and synonyms ("review my answer", "comment on your reply") rather than only the tool name.

DimensionReasoningScore

Specificity

Names the domain (annotation-driven revision) and 1-2 concrete actions ("Open Plannotator on the latest rendered assistant message", "use the returned annotations to revise that message or continue"), but the action set is not comprehensive.

3 / 5

Completeness

A clear "what" is present but there is no explicit "Use when..." trigger clause, which per the guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

Only technical/instructional phrasing ("Plannotator", "annotations", "revise") appears; a user would not naturally say these words to request the skill, and common natural trigger phrases are absent.

2 / 5

Distinctiveness Conflict Risk

"Plannotator" is a distinct named tool tied to a specific niche (annotating the latest rendered message), giving mostly distinct triggers with only minor overlap risk.

4 / 5

Total

12

/

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.