CtrlK
BlogDocsLog inGet started
Tessl Logo

plannotator-review

Open Plannotator's browser-based code review UI and address the returned feedback.

64

Quality

75%

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

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a tight, well-structured single-purpose skill: one executable command, a clear sequenced workflow with conditional handling, and no padding. It fully respects Claude's competence and token budget.

DimensionReasoningScore

Conciseness

The body is lean: a one-line trigger, a single executable command, four short behavior steps, and one guardrail line, with no explanation of concepts Claude already knows; every token earns its place.

3 / 3

Actionability

It provides a fully executable, copy-paste-ready command 'plannotator review [optional-pr-url]' plus concrete, ordered behavior steps, leaving no ambiguity about what to run.

3 / 3

Workflow Clarity

As a simple single-purpose skill under 50 lines, its four-step sequence with explicit conditional branching (feedback vs approval/LGTM) is clear and well-organized; the operation is read-only so no destructive/batch validation checkpoint is required.

3 / 3

Progressive Disclosure

At under 50 lines with no need for external references (no bundle files present), the content is organized into clearly labeled sections (trigger, Run, Behavior, guardrail), satisfying the simple-skill allowance for a top score.

3 / 3

Total

12

/

12

Passed

Description

50%

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 names a specific tool and a concrete entry action, giving it a clear niche, but it omits an explicit 'Use when…' trigger and leaves the follow-up action vague. Natural keywords are present but partial, leaving moderate conflict risk with generic review requests.

Suggestions

Add an explicit 'Use when…' clause, e.g. 'Use when the user wants a Plannotator code review of the current worktree or a PR instead of an inline diff.'

Replace the vague 'act on the feedback that comes back' with a more specific outcome, e.g. 'then resolve the returned annotations in the same conversation.'

Broaden trigger terms to include natural phrasings like 'review my changes', 'PR', or 'diff'.

DimensionReasoningScore

Specificity

Names the domain (code review) and a concrete entry action ('Open Plannotator's browser-based code review UI for the current worktree or a pull request URL'), but the second action 'act on the feedback that comes back' is vague, so it is not a comprehensive list of specific actions.

2 / 3

Completeness

It clearly answers 'what' (open the review UI and act on feedback) but provides no explicit 'Use when…' trigger guidance, so completeness is capped at 2 per the judging guidelines.

2 / 3

Trigger Term Quality

Includes natural terms like 'code review' and 'pull request URL', but misses common variations a user would actually say such as 'PR', 'review my changes', or 'diff', so coverage is partial.

2 / 3

Distinctiveness Conflict Risk

The named tool 'Plannotator' gives it a specific niche, but because the description lacks an explicit 'use when the user wants Plannotator' trigger, generic 'review my code' requests could still cause overlap with other review skills.

2 / 3

Total

8

/

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.