CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

plannotator-last

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

68

Quality

85%

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

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 exemplary lean instruction skill: one executable command, explicit handling of every possible session outcome, and valuable non-obvious guardrails (no preamble, dismissed ≠ approval, notes on approval are guidance). Nothing is padded and nothing essential is missing.

DimensionReasoningScore

Conciseness

The ~30-line body is lean with every sentence carrying non-obvious operational knowledge (why a preamble would be mis-annotated, that closing the session is not approval, that approved notes are guidance not change requests). No known concepts are over-explained and nothing could be trimmed without losing information.

5 / 5

Actionability

The skill provides a copy-paste-ready command (`PLANNOTATOR_ORIGIN=mistral-vibe plannotator last`) plus exact outcome signatures (empty output, `"decision": "dismissed"`, `"decision": "approved"` with a `"feedback"` field), covering all common cases with concrete, executable guidance.

5 / 5

Workflow Clarity

This is a simple single-action skill with an unambiguous command and an explicit numbered branch for every outcome (feedback, dismissed/empty, approved-with-notes), which meets the simple-skill exception; the destructive/batch validation cap does not apply.

5 / 5

Progressive Disclosure

The skill is under 50 lines with no need for external references (no references/scripts/assets bundle exists), and its content is well organized into an intro, a command block, and a numbered behavior list — meeting the under-50-line exception for a top score.

5 / 5

Total

20

/

20

Passed

Description

62%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.

A specific, distinctive description that clearly states what the skill does, but it lacks any explicit "use when" trigger guidance and natural-language synonyms, which limits discoverability and completeness. It reads as a capability statement rather than a triggerable description.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to annotate, mark up, or review the latest assistant response in Plannotator."

Include natural synonyms users might say ("annotate", "mark up", "comment on", "review") to improve trigger-term coverage.

Briefly mention the outcome branches (revise per feedback vs. continue) so the "what" coverage is comprehensive.

DimensionReasoningScore

Specificity

The description lists several concrete actions — "Open Plannotator on the latest rendered assistant message", "use the returned annotations to revise that message or continue" — which goes beyond the 1-2 actions of anchor 3, though coverage is not fully comprehensive (e.g., the dismissed/approved outcomes are unstated). It uses third-person-style imperative voice with no person-penalty.

4 / 5

Completeness

The "what" is clear (open Plannotator on the latest message and use its annotations to revise or continue), but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Relevant natural terms are present ("Plannotator", "annotations", "assistant message", "revise") but common variations and synonyms users might say ("mark up", "comment on", "review the response") are missing, matching anchor 3 rather than the fuller coverage of anchor 4.

3 / 5

Distinctiveness Conflict Risk

"Plannotator" is a distinctive proper noun and "latest rendered assistant message" narrows the niche further, giving clear distinct triggers and minimal conflict risk with other skills.

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

backnotprop/plannotator

Path

apps/vibe/skills/plannotator-last/SKILL.md

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.