CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

code-review

Architectural review of written code: coding standards, SOLID, testability, performance.

Quality

79%

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

Quality

Content

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

A dense but highly operational skill body: every phase gives concrete, executable instructions with explicit validation gates and fallback states, and the one external reference is well-placed and correctly load-shedded. The only trimming opportunities are a handful of justification passages that restate why a rule exists.

Suggestions

Tighten the extended rationale blocks (the 'Why this is mandatory' blockquote in Phase 7, the v1.0 migration history in Phase 2, and the false-clean-pass anecdote in the preamble) to one line each — the rules themselves already carry the guidance.

DimensionReasoningScore

Conciseness

The body never explains concepts Claude already knows (no SOLID tutorial, no ADR definition) and stays operational throughout, but a few extended rationale passages — 'Why this is mandatory', the v1.0 migration history in Phase 2, and the 16.67ms anecdote — could be trimmed without losing guidance value.

4 / 5

Actionability

Guidance is fully executable: exact commands ('git log --oneline -- [file]', grep '^## ' with line numbers), a copy-ready output template, a first-match-wins verdict ladder, concrete FOUND/ABSENT input checks, and word-for-word Phase 9 prompts covering every verdict branch and edge case (null specialists, missing ADR, no engine configured).

5 / 5

Workflow Clarity

Nine clearly sequenced phases with explicit validation checkpoints (input existence check before any report, bounded ADR reads with fallbacks, helper-result field validation, verify-every-engine-finding loop) and feedback loops (fix-then-re-run /code-review, re-validate ADR revisions); the read-only scope means no destructive-operation cap applies.

5 / 5

Progressive Disclosure

The single bundle reference (references/lens-engine.md) is real, one level deep, clearly signaled by full path with a 'do not load it here' guard, and carries exactly the detail-heavy content that belongs outside SKILL.md; the remaining body is dense inline process material that is well-sectioned but could arguably split further, keeping this just below the ideal anchor.

4 / 5

Total

18

/

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 compact and names concrete review areas, but it omits any 'when to use' trigger guidance, which both caps completeness and weakens its ability to fire for the right request. It is also generic enough to collide with other code-review-style skills.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to review, audit, or approve code, or mentions coding standards, SOLID, or architecture compliance.'

Mention the review's distinctive outputs (verdict ladder, ADR compliance check, engine-specialist review) to separate it from generic code-review skills.

Include natural user phrasings such as 'code review' or 'code quality' among the trigger terms to improve match coverage.

DimensionReasoningScore

Specificity

'coding standards, SOLID, testability, performance' names four concrete review activities, exceeding anchor 3's 1-2 actions, but coverage gaps (no mention of ADR compliance, engine review, or architecture verdicts the skill actually performs) keep it below the comprehensive anchor 5.

4 / 5

Completeness

The 'what' is clear (architectural review across four named areas) but there is no 'Use when...' clause or any equivalent explicit trigger guidance — the rubric guideline caps completeness at 3 in that case.

3 / 5

Trigger Term Quality

Phrases like 'review of written code', 'coding standards', 'SOLID', and 'performance' are terms users naturally say, giving good keyword coverage; common variations such as 'code quality', 'best practices', or 'review my code' are missing, which anchor 5 requires.

4 / 5

Distinctiveness Conflict Risk

'review of written code' is broad and would overlap generic code-review, code-quality, or refactoring skills, though the SOLID/testability focus narrows it somewhat — matching anchor 3's 'somewhat specific but could still overlap with similar skills'.

3 / 5

Total

14

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository

Donchitos/Claude-Code-Game-Studios

Path

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