CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

code-review

Brutally honest code review assessing security, reliability, performance, and taste

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.opencode/skills/code-review/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 highly actionable — concrete prompt and report templates, explicit severity scheme, and specific examples — with a clear orchestration sequence. Its main weaknesses are heavy self-duplication (the same dispatch/aggregate/write workflow appears four times and the criteria twice) and a monolithic single-file layout that inlines per-pass criteria which belong in reference files.

Suggestions

Collapse 'Your Task', 'Execution Strategy', 'Review Process (Orchestrator)', and 'Begin' into one canonical workflow section — roughly a third of the body is repetition of the same steps.

Merge 'Subagent Review Criteria' into 'Review Criteria' (or split each pass's criteria into per-pass reference files) since the two sections restate the same dimensions, and fold 'Guidelines' into 'Review Principles'.

Add an explicit validation step before writing the report, e.g. 're-verify each critical/high finding against the cited file:line before including it', to create a feedback loop and raise workflow clarity.

Move the output report template to a reference file (e.g. references/report-template.md) and link it one level deep, keeping SKILL.md as a lean orchestration overview.

DimensionReasoningScore

Conciseness

The ~350-line body states the same workflow four times ('Your Task', 'Execution Strategy', 'Review Process (Orchestrator)', 'Begin') and restates the review criteria twice ('Review Criteria' vs. 'Subagent Review Criteria', plus 'Guidelines' duplicating 'Review Principles') — several whole padded sections that could be cut. It is not 1 because no section explains concepts Claude already knows and each individual passage is purposeful instruction rather than textbook padding; it is not 3 because this is wholesale duplicated structure, not minor tightening.

2 / 5

Actionability

The skill provides a copy-paste-ready subagent prompt template, a complete output report template with severity levels, concrete good/bad finding examples ('regex on line 34 is vulnerable to ReDoS with input like \'a\'.repeat(50)'), and an exact report path (`.agents/scratch/code-review-<scope>.md`). As an instruction-only skill its guidance is fully executable with the common cases covered, matching the anchor-5 example; there are no missing key details that would drop it to 4.

5 / 5

Workflow Clarity

The sequence (identify scope → gather context → parallel dispatch → deduplicate/assign severity → write report) is clearly laid out with checkpoints such as deduplication and severity reconciliation ('if subagents disagreed, use the higher severity'). It is not 5 because there is no explicit validation/feedback loop — e.g. verifying reported findings against the actual code before publishing the report — and not 3 because the sequence and aggregation checkpoints are explicit and the operation is non-destructive, so no cap applies.

4 / 5

Progressive Disclosure

The single 350-line file has good in-document structure (clear headers, numbered criteria), but no bundle files exist and everything is inlined — including the four per-pass criteria sections that the skill itself says to splice into individual subagent prompts, which would naturally live as one-level-deep reference files. It is not 2 because the body is well-sectioned rather than an unstructured wall, and not 4 because at this length the per-pass criteria and output template are strong candidates for separate files and no disclosure structure exists at all.

3 / 5

Total

14

/

20

Passed

Description

62%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 four concrete review dimensions, but it answers only 'what' — there is no explicit 'when to use' guidance and no mention of the report output. Adding a 'Use when...' clause with natural trigger phrases would lift completeness and trigger-term quality simultaneously.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to review code, a diff, or a PR, or wants an honest assessment of code quality, bugs, or security issues.'

State the concrete output action — e.g. 'produces a severity-ranked findings report' — so the 'what' covers the deliverable, not just the assessment dimensions.

Include natural synonyms such as 'code quality', 'find bugs', or 'audit' to reduce overlap ambiguity with general review and security-review skills.

DimensionReasoningScore

Specificity

The description lists several concrete review dimensions — "assessing security, reliability, performance, and taste" — which gives specific coverage of what is evaluated, though it omits the concrete output action (producing a prioritized findings report). It sits between anchor 3 (domain + 1-2 actions) and anchor 4 (several specific actions, minor gaps): four named assessment areas plus the 'code review' action exceed anchor 3, while the missing report-output mention keeps it below anchor 5.

4 / 5

Completeness

The 'what' is clearly stated (honest code review across security, reliability, performance, and taste), but there is no 'Use when...' clause or any equivalent explicit trigger guidance — the when is entirely absent, not merely weakly implied. Per the judging guidelines, a missing 'Use when' clause caps completeness at 3, which matches anchor 3 exactly and rules out 4.

3 / 5

Trigger Term Quality

"code review" plus "security", "reliability", "performance", and "taste" are terms a user would naturally say when needing this skill, giving good keyword coverage. It is not 5 because common natural variations like "review my code", "find bugs", "code quality", or "audit" are absent, and not 3 because the primary trigger phrase plus four dimension keywords go beyond minimal coverage.

4 / 5

Distinctiveness Conflict Risk

"Brutally honest code review" carves out a recognizable tone but the underlying trigger ('code review', 'security') overlaps heavily with other review, audit, and security-review skills, so it could still trigger for the wrong skill. It is above anchor 2 (purely broad, e.g. 'helps with code') because the named dimensions add specificity, but below anchor 4 because 'security' assessment and generic 'code review' have real overlap with closely related skills.

3 / 5

Total

14

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

LibPDF-js/core

Path

.opencode/skills/code-review/SKILL.md

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.