CtrlK
BlogDocsLog inGet started
Tessl Logo

pr-review

Standardized guidelines and templates for structuring Pull Request reviews so feedback is actionable, encouraging, and extractable by the Native Edge Graph. MANDATORY ROI WARNING: Skipping the review template guarantees CI lint failure. Triggers: Reviewing a PR (yours or peer's) — structured eval metrics, graph ingestion tags, severity ladder, restates §0 merge gate, post-comment A2A commentId hand-off (reviewer→author) per guide §10, Evidence Audit + Source-of-Authority sections (template §) for substrate/runtime-AC PRs and authority-citation review-comments.

60

Quality

70%

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 ./.agents/skills/pr-review/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

61%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 compact, well-structured overview that delegates detail to bundled reference files — good progressive disclosure and reasonable token efficiency. Its weaknesses are inconsistent/ambiguous file paths, a missing referenced audit file, and an implicit rather than explicit workflow sequence with scattered validation checkpoints.

Suggestions

Resolve the broken reference: `audits/review-cost-circuit-breaker.md` is cited but absent from references/audits/ — either add the file or point to an existing audit (e.g. decile-anchors.md / mcp-tool-description-budget.md) if it covers budget circuit-breaking.

Use consistent, fully-qualified bundle paths for every "load" instruction (e.g. `assets/pr-review-template.md` rather than the bare `pr-review-template.md`) so the guidance is directly executable.

Re-express the review flow as a short numbered sequence (sweep → audit gate → Round 1 template → Round 2 disposition → budget check) with explicit validation checkpoints, instead of prose with inline conditional clauses.

DimensionReasoningScore

Conciseness

The body is lean and does not explain concepts Claude already knows — it jumps straight to gates, sweeps, and template loads — matching anchor 4's "efficient; minor instances that could be trimmed"; held below 5 because dense unexplained acronyms (V-B-A, A+FU, D+S, RC, §0/§10/§6.4) spend tokens on shorthand that does not fully earn its place for an unprimed reader.

4 / 5

Actionability

Gives concrete pointers ("use the `view_file` tool", "run a 3–10-call `query_raw_memories` / `query_summaries` sweep", "load pr-review-template.md") but key details are missing: template files are referenced by bare name without the `assets/` path, pathing is inconsistent with the guide reference, and `audits/review-cost-circuit-breaker.md` is referenced but does not exist in the bundle — matching anchor 3's "some concrete guidance but incomplete; missing key details".

3 / 5

Workflow Clarity

A rough sequence is present (prior-art sweep → instrument audit → Round 1 template → Round 2 → budget/disposition) but it is prose with conditional branches rather than a clearly numbered flow, and validation checkpoints ("The sweep RESULT is the V-B-A; CI-green ≠ AC-met") are implicit and scattered, matching anchor 3's "sequence present but checkpoints missing or implicit".

3 / 5

Progressive Disclosure

SKILL.md acts as an overview pointing to one-level-deep references (guide, instrument-audit, four templates, a cost audit) that are clearly signaled with "load"; the bundle is well split across references/ and assets/, matching anchor 4's "good structure; references mostly clear; minor organization gaps" — held below 5 by the broken `review-cost-circuit-breaker.md` reference and inconsistent path prefixes.

4 / 5

Total

14

/

20

Passed

Description

78%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 a strong, specific niche description with explicit what/when guidance and concrete action components. Its main weakness is heavy internal jargon (V-B-A, A2A, AC-met) that obscures the natural-language quality a trigger description should optimize for.

Suggestions

Lead the description with the plain-language "what" and "when" before the jargon-laden detail, so a user scanning skill triggers sees "Use when reviewing a Pull Request (yours or a peer's)" up front.

Expand the trigger clause beyond the single "Reviewing a PR (yours or peer's)" to include natural synonyms ("code review", "peer review", "reviewing staged changes / a diff") for better trigger-term coverage.

Move the MANDATORY ROI WARNING and section citations out of the description frontmatter and into the body; they inflate the description without aiding trigger matching.

DimensionReasoningScore

Specificity

Lists several concrete actions — "structured eval metrics, graph ingestion tags, severity ladder, restates §0 merge gate, post-comment A2A commentId hand-off, Evidence Audit + Source-of-Authority sections" — matching anchor 4's "several specific actions; minor gaps", falling short of anchor 5 only because the actions are heavily jargon-laden rather than self-evidently comprehensive.

4 / 5

Completeness

Clearly states the "what" ("guidelines and templates for structuring Pull Request reviews") and an explicit "when" ("Triggers: Reviewing a PR (yours or peer's)"), satisfying both; held at 4 rather than 5 because the trigger clause is a single terse phrase versus anchor 5's comprehensive concrete trigger phrases.

4 / 5

Trigger Term Quality

Includes natural phrases a user would say — "Pull Request reviews", "Reviewing a PR (yours or peer's)" — giving good keyword coverage, but stops short of anchor 5's comprehensive synonym/extension coverage (e.g. no "code review", "peer review" variants).

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (PR review structuring) with distinct triggers, minimal conflict risk with other skills; matches anchor 5's "clear niche with distinct triggers".

5 / 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
neomjs/neo
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.