plannotator-review

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

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./apps/kiro-cli/skills/plannotator-review/SKILL.md

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 an exemplary minimal skill: lean, fully executable, and well-organized for a single-purpose command. No changes are needed to the body.

Dimension	Reasoning	Score
Conciseness	The body is lean with no concept explanations; the only prose is a brief variant hint, and every token earns its place, matching the anchor for a lean, efficient skill.	5 / 5
Actionability	It provides a fully copy-paste-ready base command plus variant invocations covering the common cases (PR URL, base/diff-type); placeholders are justified CLI flexibility.	5 / 5
Workflow Clarity	This is a simple single-purpose skill whose single action (run `plannotator review`) is unambiguous, and it involves no destructive or batch operations that would require validation checkpoints.	5 / 5
Progressive Disclosure	At under 50 lines with no need for external references and well-organized labeled sections, it meets the simple-skill exception for progressive disclosure.	5 / 5
	Total	20 / 20 Passed

Description

53%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 concise and names a distinct tool, but it omits an explicit "Use when..." trigger clause and only lists two actions, the second of which is generic. Adding trigger phrases and a couple more concrete actions would raise its score.

Suggestions

Add a 'Use when...' clause naming natural triggers, e.g. 'Use when the user asks to run a Plannotator code review or address Plannotator review feedback.'

Expand the action list with concrete steps beyond 'open' and 'address', such as 'launch the review session, read returned comments, and apply fixes'.

Include common synonyms/users' phrasings like 'review my code', 'address review comments', or 'Plannotator review'.

Dimension	Reasoning	Score
Specificity	Names the code-review domain and two actions ("Open... UI" and "address the returned feedback"), but the second action is generic and only two actions are listed, matching the anchor for 1-2 concrete actions.	3 / 5
Completeness	It clearly states what the skill does but provides no "Use when..." trigger clause, which per the guidelines caps completeness at 3.	3 / 5
Trigger Term Quality	"code review", "review", and "feedback" are natural terms, but there are no explicit trigger phrases and common synonyms/variations are missing.	3 / 5
Distinctiveness Conflict Risk	Naming the specific tool "Plannotator" gives it a clear niche with only minor overlap risk against generic code-review skills.	4 / 5
	Total	13 / 20 Passed

Validation

100%

Warnings & errors only

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/kiro-cli/skills/plannotator-review/SKILL.md
Commit: 8f2a8a8

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.