CtrlK
BlogDocsLog inGet started
Tessl Logo

local-review

Code review the current PR (or branch diff against main) for bugs, security, and AGENTS.md compliance. MUST use when asked to review code.

75

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

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.

A tight, highly actionable review skill: executable commands, exact templates, a clear numbered workflow with a self-validation checkpoint, and well-sectioned organization. No bundle files are needed and none are referenced as skill-internal files, so progressive disclosure is satisfied by the clean section structure.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence: concrete steps, exact templates, and specific commands with no padding explaining what code review or PRs are. The "Why a subagent" rationale earns its place by justifying a non-obvious design decision rather than restating common knowledge.

3 / 3

Actionability

Provides copy-paste-ready executable commands throughout (gh pr view/diff, git rev-parse, git diff main...<branch>, gh pr review, gh api …) plus exact output-format and subagent-prompt templates, matching the fully-executable anchor.

3 / 3

Workflow Clarity

A clearly numbered 4-step sequence with an explicit validation checkpoint: the subagent self-validates each finding ("is this definitely a real issue… Discard if uncertain") and the main session relays verbatim, giving a feedback loop for error recovery.

3 / 3

Progressive Disclosure

The content is well-organized into clearly signaled sections (Steps, Subagent prompt template, Output format, Posting comments) with inline references only to repo-level policy files (REVIEW.md, AGENTS.md) that are not part of this skill bundle, keeping navigation shallow and obvious.

3 / 3

Total

12

/

12

Passed

Description

85%

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 strong, specific description that clearly states what the skill does and when to use it, with a distinct niche. Its only weakness is narrow trigger-term coverage that misses common phrasings users might actually say.

Suggestions

Broaden trigger terms to cover natural variations users would say, e.g. "Use when asked to review a PR, check a branch diff, or review code before merge."

Consider adding a short mention of the output (e.g. "…and posts inline comments with --comment") so the capability surface is fully explicit.

DimensionReasoningScore

Specificity

Names multiple concrete actions — "Code review the current PR (or branch diff against main) for bugs, security, and AGENTS.md compliance" — matching the anchor that lists several specific concrete actions rather than vague language.

3 / 3

Completeness

It explicitly answers both what (review PR/branch diff for bugs, security, AGENTS.md compliance) and when ("MUST use when asked to review code"), matching the anchor that clearly answers both with an explicit trigger.

3 / 3

Trigger Term Quality

"MUST use when asked to review code" gives a natural trigger but the keyword coverage is narrow (only "review code"), missing common variations users would say like "review my PR", "check this diff", or "look at this branch".

2 / 3

Distinctiveness Conflict Risk

The PR/branch-diff code-review niche with AGENTS.md compliance is specific and distinct, unlikely to trigger for unrelated skills, matching the clear-niche anchor.

3 / 3

Total

11

/

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
windmill-labs/windmill
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.