CtrlK
BlogDocsLog inGet started
Tessl Logo

code-review

Review code for bugs, security issues, performance problems, and best practices. Provide actionable feedback.

58

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 ./apps/desktop/bundled-skills/code-review/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 lean, well-organized checklist with a concrete output format and clear single-action workflow. Its main gap is actionability: the checklist items are generic and lack a worked review example showing the expected output.

DimensionReasoningScore

Conciseness

The body is a lean checklist plus a compact output format with no padding and no explanation of concepts Claude already knows; every section earns its place.

3 / 3

Actionability

The output format (Location, Severity, Issue, Fix) is concrete, but the checklist items ('Logic errors', 'Code clarity') are generic and there is no worked example of an actual review output, leaving guidance incomplete.

2 / 3

Workflow Clarity

This is a simple single-task skill whose action — review against the listed categories and report findings in the four-field format — is unambiguous, which the simple-skills note allows to score 3.

3 / 3

Progressive Disclosure

The skill is under 50 lines, needs no external references, and is organized into clear sections (Checklist, Output Format, Examples), satisfying the simple-skill 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 states what the skill does with reasonable specificity but omits any explicit 'when to use it' trigger guidance, leaving all dimensions at the mid-level. It is competent but generic and would benefit from explicit trigger terms.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when the user asks to review code, a PR, or a pull request for bugs, security issues, or performance problems.'

Expand trigger terms with natural user phrasings like 'PR review', 'pull request', 'find bugs', and 'check my code'.

Differentiate the skill from generic debugging/linting by naming its distinctive output (e.g. 'Produces a prioritized list of issues with file, line, severity, and fix').

DimensionReasoningScore

Specificity

Names the code-review domain and several review targets ('bugs, security issues, performance problems, and best practices') plus 'Provide actionable feedback', but the action verbs are limited (review/provide) rather than multiple distinct concrete actions, matching the 'names domain and some actions, but not comprehensive' anchor.

2 / 3

Completeness

It clearly answers 'what' the skill does but lacks any 'Use when...' or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 2.

2 / 3

Trigger Term Quality

'Review code', 'bugs', and 'security issues' are terms a user might say, but common variations like 'PR', 'pull request', 'find issues', or 'check my code' are missing, so coverage is partial.

2 / 3

Distinctiveness Conflict Risk

'Review code for bugs, security issues, performance problems, and best practices' is a common niche that could overlap with dedicated debugging, security-audit, or linting skills rather than being a clearly distinct trigger.

2 / 3

Total

8

/

12

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.

Validation15 / 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
accomplish-ai/coworker
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.