CtrlK
BlogDocsLog inGet started
Tessl Logo

code-reviewer

Code review specialist focused on patterns, bugs, security, and performance

59

Quality

67%

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 ./crates/openfang-skills/bundled/code-reviewer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%

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, actionable instruction skill whose checklists provide concrete review guidance; its only weakness is that some general reviewing advice reiterates what Claude already knows.

DimensionReasoningScore

Conciseness

The security and performance checklists are lean and concrete, but the 'Key Principles' and 'Communication Style' sections restate general reviewing practices Claude already knows (e.g. 'Prioritize feedback by severity', 'Use a neutral, professional tone'), so the content is mostly efficient but includes guidance that could be tightened.

2 / 3

Actionability

The checklists give specific, executable review checks ('are queries parameterized, or is string interpolation used?', 'are database calls made inside loops?', 'are API keys, passwords, or tokens hardcoded or logged?'); as an instruction-only skill, the absence of code is not penalized and the guidance is concrete.

3 / 3

Workflow Clarity

A clear priority sequence ('security issues first, then correctness bugs, then performance, then style') plus structured checklists give a clear order; as a single-purpose skill under 50 lines with no destructive operations, no validation feedback loop is required.

3 / 3

Progressive Disclosure

The skill is under 50 lines, requires no external references, and is organized into well-labeled sections (Key Principles, Security Review Checklist, Performance Review Checklist, Communication Style, Pitfalls to Avoid), meeting the simple-skills allowance for a top score.

3 / 3

Total

11

/

12

Passed

Description

50%

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 clearly identifies the skill's domain and focus areas but relies on abstract phrasing and omits any 'Use when' trigger guidance, leaving every dimension at the middle anchor.

Suggestions

Add an explicit 'Use when' clause stating when to invoke the skill, e.g. 'Use when the user asks to review code, find bugs, or check security and performance issues.'

Replace the abstract 'focused on' with concrete action verbs, e.g. 'Reviews code for bugs, security vulnerabilities, performance issues, and anti-patterns.'

Broaden trigger terms to cover natural variations users say, such as 'vulnerabilities', 'audit', and 'review my code'.

DimensionReasoningScore

Specificity

The description names a concrete domain ('code review') plus four sub-areas ('patterns, bugs, security, and performance'), but uses the abstract phrase 'focused on' with no action verbs, so it names topics rather than concrete actions and does not reach the 'multiple specific concrete actions' anchor.

2 / 3

Completeness

It states what the skill does but has no 'Use when...' clause or equivalent explicit trigger guidance, so per the judging guideline the 'when' is missing and completeness is capped at 2.

2 / 3

Trigger Term Quality

'code review', 'bugs', 'security', and 'performance' are terms a user might naturally say, but coverage is incomplete — common variations like 'vulnerabilities', 'audit', or 'review my code' are missing, matching 'some relevant keywords but missing common variations'.

2 / 3

Distinctiveness Conflict Risk

'Code review specialist' carves out a recognizable niche, but without explicit trigger phrases it could still overlap with general coding/analysis skills, fitting 'somewhat specific but could still overlap with similar skills'.

2 / 3

Total

8

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
RightNow-AI/openfang
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.