CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

code-reviewer

Elite code review expert specializing in modern AI-powered code

Quality

43%

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-reviewer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

28%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 persona document — a generic capability catalog with no executable guidance, commands, code examples, or validation steps. It reads like a résumé for the agent rather than an operational skill, so Claude learns nothing actionable from loading it.

Suggestions

Replace the capability/trait/knowledge enumerations with a concrete review workflow: actual commands (e.g. `semgrep --config auto .`, `npm audit`) and a severity-classified findings format.

Add validation checkpoints and feedback loops to the workflow (e.g. re-run analysis after fixes, verify findings against the diff before reporting).

Move language-specific expertise and tool catalogs into references/ files linked one level deep from SKILL.md, keeping only the workflow and decision rules inline.

DimensionReasoningScore

Conciseness

The ~170-line body is padded with sections enumerating knowledge Claude already has ("Clean Code principles and SOLID pattern adherence", "OWASP Top 10 vulnerability detection", "Behavioral Traits", "Knowledge Base") with no new procedural value. This matches anchor 2 (noticeably verbose, several padded sections) rather than 1, since it is list-padding rather than extensive explanatory prose.

2 / 5

Actionability

No executable code or commands appear anywhere; tools are name-dropped ("SonarQube, CodeQL, and Semgrep", "npm audit, pip-audit") without invocation guidance. The "Response Approach" steps ("Apply automated tools for initial analysis") are high-level hints missing specific steps, matching anchor 2 rather than 1 because a rough process sequence exists.

2 / 5

Workflow Clarity

The 10-step "Response Approach" provides a rough sequence but steps are abstract ("Conduct manual review", "Assess security implications") with no validation checkpoints or error-recovery loops. This matches anchor 2 (rough sequence, poorly defined steps, validation absent), not 3, which requires concretely defined steps.

2 / 5

Progressive Disclosure

The body is well-sectioned with headers, but large blocks that belong in separate reference files (language-specific expertise, tool catalogs, example interactions) are fully inlined and no bundle files exist. This sits between anchor 2 (inlined content, minimal structure) and anchor 4 (appropriately placed content), matching anchor 3: structure present but content that should be separate is inline.

3 / 5

Total

9

/

20

Passed

Description

32%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 buzzword-heavy persona label rather than a functional skill description. It fails to state concrete actions, trigger conditions, or a distinct niche, and would rarely be selected correctly based on it alone.

Suggestions

Replace the persona phrasing with concrete actions, e.g. "Reviews code for security vulnerabilities (OWASP Top 10), performance issues, and maintainability; runs static analysis with Semgrep/CodeQL".

Add an explicit trigger clause: "Use when the user asks to review code, a pull request, a diff, or a migration, or mentions code quality, security review, or PR feedback".

Sharpen the niche (e.g. production-readiness or security-focused review) to reduce overlap with generic code-review skills.

DimensionReasoningScore

Specificity

The description "Elite code review expert specializing in modern AI-powered code" names the domain (code review) but contains no concrete actions, relying on buzzwords like "Elite" and "modern AI-powered". It sits between anchor 1 (pure abstraction) and anchor 3 (1-2 concrete actions), matching anchor 2: domain named, actions minimal or generic.

2 / 5

Completeness

There is no "Use when..." clause or equivalent trigger guidance, and the "what" is vague ("specializing in modern AI-powered code"). This matches anchor 2 (vague 'what' and no 'when'), not 3, which requires a clear 'what'.

2 / 5

Trigger Term Quality

"code review" is a phrase users would naturally say, but it is the only trigger term; common variations like "review my PR", "pull request", or "review this diff" are absent. This matches anchor 3 (some relevant keywords, missing common variations) rather than 4, which requires good keyword coverage.

3 / 5

Distinctiveness Conflict Risk

"code review expert" is very broad and would overlap with many similar review/QA skills; nothing distinguishes it (no niche like a specific language, tool, or workflow). This matches anchor 2 (very broad; high overlap risk) rather than 3, which requires some specificity.

2 / 5

Total

9

/

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