CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

code-review-excellence

Transform code reviews from gatekeeping to knowledge sharing through constructive feedback, systematic analysis, and collaborative improvement.

Quality

56%

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

Quality

Content

57%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 well-organized, concise overview with a clear scope (use/do-not-use) and a concrete output format, but its instructional core stays at the level of high-level directives with no examples or checklists. Its one progressive-disclosure reference points to a file that is missing from the bundle, so the promised detail is unreachable.

Suggestions

Fix the dangling reference: either add `resources/implementation-playbook.md` to the bundle or remove/inline the checklist content it promises.

Add one or two concrete examples of actionable feedback (e.g., a sample finding with severity, rationale, and suggested fix) to ground the abstract directives in Instructions.

Define the severity tiers (blocking/important/minor) with one-line criteria so the Output Format is directly executable rather than interpretive.

DimensionReasoningScore

Conciseness

The body is lean and well-sectioned with no explanations of concepts Claude already knows; the main trim candidates are the tagline duplicated verbatim from the description and the somewhat generic Limitations bullets ("Do not treat the output as a substitute for..."). This matches anchor 4 (efficient, minor instances that could be trimmed), not 5, due to that duplication and filler.

4 / 5

Actionability

The Output Format section is concrete (severity tiers 'blocking, important, minor', defined sections), but the Instructions are high-level directives — "Provide actionable feedback with severity and rationale" is itself abstract — with no examples of good feedback, severity definitions, or review checklists. It sits between anchor 2 (high-level hints, missing steps) and anchor 3 (some concrete guidance, incomplete), and the concrete output template justifies 3.

3 / 5

Workflow Clarity

Instructions imply a sequence ("Read context, requirements, and test signals first" → review → give feedback) but ordering beyond the first step is implicit, and the detailed process is deferred to a playbook file that does not exist in the bundle. This matches anchor 3 (sequence present, checkpoints missing or implicit); it is not a destructive/batch operation, so no hard cap applies, but anchor 4's 'most checkpoints present' is not met.

3 / 5

Progressive Disclosure

Sections are clearly organized (Use when / Do not use when / Instructions / Output Format / Resources / Limitations), but the sole reference — `resources/implementation-playbook.md` — is a dangling pointer: no such file exists in the bundle (no references/, scripts/, or resources/ directory). Anchor 3 (structure present, references present but problematic) fits; the broken reference prevents a 4 despite the good section organization.

3 / 5

Total

13

/

20

Passed

Description

36%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 reads as a vision statement rather than a capability description: it names the code review domain but lists no concrete actions and gives no 'use when' trigger guidance. Users searching for help with a PR review might not surface this skill, and it risks overlap with other review-related skills.

Suggestions

Rewrite the description to list concrete capabilities in third person, e.g., 'Reviews pull requests and code changes for correctness, security, performance, and maintainability; groups findings by severity with actionable fixes.'

Add an explicit trigger clause: 'Use when reviewing pull requests, diffs, staged changes, or when asked to give code review feedback.'

Include natural synonyms such as 'pull request', 'PR', and 'diff' to improve trigger-term coverage and distinctiveness from generic feedback skills.

DimensionReasoningScore

Specificity

The description names the domain ("code reviews") but its actions are generic qualities — "constructive feedback, systematic analysis, and collaborative improvement" — rather than concrete capabilities like reviewing PRs or categorizing findings. It matches anchor 2 (domain named, actions minimal or generic), not 3, because no concrete action is actually listed.

2 / 5

Completeness

There is no "Use when..." clause or equivalent trigger guidance, and the "what" is a mission statement ("Transform code reviews from gatekeeping to knowledge sharing") rather than a capability list. This matches anchor 2 (vague 'what' and no 'when'), not 3, because the 'what' lacks concrete actions; the missing trigger clause also caps the score per the guidelines.

2 / 5

Trigger Term Quality

"code reviews" is a natural phrase users would say, but common variations and synonyms ("pull request", "PR", "diff", "changes") are absent. This fits anchor 3 (some relevant keywords, missing variations) better than 2, since the included keyword is the domain's natural term rather than generic filler.

3 / 5

Distinctiveness Conflict Risk

"Code reviews" identifies a recognizable niche, but code review is a very common skill category (e.g., built-in review tooling) and no distinguishing triggers or scope markers separate it from those. Anchor 3 (somewhat specific, could overlap with similar skills) is the best fit — not 4, since overlap risk with closely related review skills is more than minor.

3 / 5

Total

10

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

BigSimmo/Communication

Path

.agents/skills/code-review-excellence/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.