CtrlK
BlogDocsLog inGet started
Tessl Logo

plannotator-review

Open Plannotator's browser-based code review UI for the current worktree or a pull request URL, then act on the feedback that comes back.

64

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./apps/skills/claude/plannotator-review/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 a model of a lean, single-purpose skill: a concrete auto-executing command with documented arguments and a clear two-branch follow-up, with no unnecessary padding or nested references.

DimensionReasoningScore

Conciseness

The body is lean and efficient with no padded explanation of concepts Claude already knows; every line (argument pass-through, the runnable command, the follow-up handling) earns its place.

5 / 5

Actionability

The auto-executing '!`plannotator review $ARGUMENTS`' command is copy-paste ready and concrete, with the supported arguments documented specifically; common cases are fully covered.

5 / 5

Workflow Clarity

This is a simple single-purpose skill whose one action (run the review) is unambiguous, with a clearly bifurcated follow-up (address feedback vs. acknowledge an approval); the simple-skill exception applies and the operation is not destructive/batch.

5 / 5

Progressive Disclosure

At well under 50 lines with no need for external references, the content is organized into clear sections (overview, Code review feedback, Your task), satisfying the simple-skill exception for a top score.

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 specific and tool-anchored with clear actions, but it lacks an explicit 'Use when...' trigger clause and omits common synonym keywords (PR/MR/diff), capping several dimensions at 3.

Suggestions

Add an explicit 'Use when...' clause stating when to invoke this skill (e.g. 'Use when the user asks to review a PR/MR URL or the current worktree with Plannotator').

Include natural synonym keywords users actually say — PR, MR, merge request, diff — alongside 'pull request URL' to improve trigger term coverage.

List a couple more concrete actions (e.g. viewing annotations, iterating on fixes) to lift specificity toward comprehensive coverage.

DimensionReasoningScore

Specificity

Names the domain (Plannotator code review) and two concrete actions ('Open... browser-based code review UI', 'act on the feedback that comes back'), but coverage is not comprehensive enough for a 4 which requires several specific actions.

3 / 5

Completeness

It clearly states what the skill does, but there is no explicit 'Use when...' trigger clause, so the 'when' is only weakly implied; the missing-trigger-clause guideline caps completeness at 3.

3 / 5

Trigger Term Quality

Relevant keywords are present ('code review', 'pull request URL', 'worktree'), but common variations and synonyms a user might say (PR, MR, merge request, diff) are missing.

3 / 5

Distinctiveness Conflict Risk

Tying the skill to the named tool 'Plannotator' and its browser-based UI gives it a clear niche, but the generic 'code review' framing leaves minor overlap risk with other review skills, fitting anchor 4 rather than 5.

4 / 5

Total

13

/

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.