CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

review-maintainability-and-code-quality

Review a code change for maintainability, naming, weak contracts, duplicated local precedent, misleading comments, and API or code surfaces that do not enforce what they promise. Use when reviewing for readability, refactoring, code quality, or API design issues.

1.08x
Quality

87%

Does it follow best practices?

Impact

98%

1.08x

Average score across 18 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

The canonical home for this skill is tessl/code-review

SKILL.md
Quality
Evals
Security

Quality

Content

86%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 well-crafted instruction-only skill body: dense, assumption-respecting prose with specific review moves and concrete reporting requirements ('State the structural fix, not "add a comment"'). The only notable gap is the absence of a worked example illustrating what a good finding looks like.

DimensionReasoningScore

Conciseness

The ~35-line body is lean and assumes Claude's competence — no basic-concept explanations, no padding; every line instructs (e.g., 'a helper, schema or convention the codebase already has and this one rebuilds'). It matches the anchor: every token earns its place.

5 / 5

Actionability

For an instruction-only skill the guidance is specific and executable: 'Read each new or changed name against what the code behind it does', 'read the signature and its description as a consumer who cannot see the implementation', 'name the precedent with its file path'. It falls short of 5 only because no worked example of a finding is given to cover common cases.

4 / 5

Workflow Clarity

The Method section sequences the review (read the AGENTS.md/CLAUDE.md chain, then names vs. behavior, then public boundaries, then contract enforcement) and includes a checkpoint ('Before suggesting reuse, verify that the existing code is the appropriate precedent'). This is a read-only skill so the destructive-operation validation cap does not apply; it misses 5 for lacking an explicit feedback/recovery loop.

4 / 5

Progressive Disclosure

Under 50 lines, no external references needed, and no bundle files exist; the body is cleanly organized into Scope, Method, Threshold, and Reporting sections. Per the simple-skill guideline, this earns a 5 with well-organized sections alone.

5 / 5

Total

18

/

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 description: third-person, concrete about what it reviews, with an explicit and well-phrased 'Use when' trigger clause covering natural user language. Its only weaknesses are the single-verb action framing and a few missing trigger synonyms.

DimensionReasoningScore

Specificity

Lists six concrete review targets ('maintainability, naming, weak contracts, duplicated local precedent, misleading comments, and API or code surfaces that do not enforce what they promise'), giving specific coverage with only minor gaps. It stays at 4 rather than 5 because the action is a single verb ('Review') applied to many objects rather than multiple distinct concrete actions, and it is above 3 because the enumerated targets are specific, not generic.

4 / 5

Completeness

Clearly answers both parts: a concrete 'what' (the enumerated maintainability, naming, contract, and comment checks) followed by an explicit 'Use when reviewing for readability, refactoring, code quality, or API design issues' trigger clause. Not a 4 because the 'when' is already explicit and specific with concrete trigger phrases.

5 / 5

Trigger Term Quality

'Use when reviewing for readability, refactoring, code quality, or API design issues' supplies natural phrases users would actually say. A few natural variants are missing (e.g., 'code smells', 'clean up code', 'maintainability' as a trigger), keeping it below the comprehensive synonym coverage of a 5.

4 / 5

Distinctiveness Conflict Risk

The maintainability/quality framing ('weak contracts', 'duplicated local precedent', 'surfaces that do not enforce what they promise') carves a distinct niche apart from correctness-bug or security review. Minor overlap risk remains with generic 'code review' skills via the broad phrase 'code quality', so it does not reach the minimal-conflict clarity of a 5.

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

tesslio/product-plugins

Path

code-review/skills/review-maintainability-and-code-quality/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.