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.

66

Quality

79%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/local-review/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 efficient, actionable, well-sequenced guide to running a fresh-context subagent review with concrete gh/git commands and templates. It scores consistently strong across all dimensions with only minor gaps in copy-paste readiness and absent-PR handling.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence; the "Why a subagent" paragraph earns its place by surfacing non-obvious rationale, with only minor trimming possible in the template prose.

4 / 5

Actionability

Concrete commands (`gh pr view <n>`, `git diff main...<branch>`, `gh api ... reviews`) and a specific subagent_type are given, but the prompt template uses placeholders like `<PR #N | branch X>` rather than copy-paste-ready text.

4 / 5

Workflow Clarity

A clear 4-step sequence with explicit checkpoints (confirm PR/branch exists in step 1, subagent self-validates findings) and a feedback loop; minor gap in not stating what to do when the PR/branch is absent.

4 / 5

Progressive Disclosure

Well-organized into Steps, Subagent prompt template, Output format, and Posting comments; no bundle files exist so it is a single-file skill, and the external REVIEW.md/AGENTS.md are repo policy rather than skill bundle references.

4 / 5

Total

16

/

20

Passed

Description

83%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 strong, specific description that concretely states both the review scope and an explicit use-trigger. It is concise and third-person, with only minor synonym/coverage gaps.

DimensionReasoningScore

Specificity

"review the current PR (or branch diff against main) for bugs, security, and AGENTS.md compliance" names the domain plus several concrete review targets and the diff scope, with only minor coverage gaps (e.g. no mention of comment posting).

4 / 5

Completeness

It explicitly states what it does (review PR/branch diff for bugs, security, AGENTS.md compliance) and when to use it ("MUST use when asked to review code"), matching the anchor for both what and when with a concrete trigger phrase.

5 / 5

Trigger Term Quality

"MUST use when asked to review code" supplies the natural phrase users say, plus "review code", "PR", and "branch diff"; a few synonyms like "code review" or "check my diff" are missing.

4 / 5

Distinctiveness Conflict Risk

The PR/branch-diff scope plus AGENTS.md compliance carve a clear niche, but "asked to review code" has minor overlap risk with other general review skills.

4 / 5

Total

17

/

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