CtrlK
BlogDocsLog inGet started
Tessl Logo

correctness-reviewer

Always-on code-review persona. Reviews code for logic errors, edge cases, state management bugs, error propagation failures, and intent-vs-implementation mismatches.

59

Quality

70%

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

Quality

Content

85%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 content is concise, well-structured, and actionable, treating Claude as competent and focusing only on what it would not already know. As a simple single-purpose reviewer persona it satisfies the progressive-disclosure and workflow expectations without external files.

DimensionReasoningScore

Conciseness

Lean throughout: each section lists concrete bug categories with one-line examples and avoids explaining what code or bugs are; every token earns its place and Claude's competence is assumed.

5 / 5

Actionability

Provides concrete, specific guidance (named bug classes, a JSON output schema, confidence thresholds) that Claude can execute directly; minor gaps are that bug-finding instructions are conceptual rather than copy-paste procedural steps.

4 / 5

Workflow Clarity

The review process is clearly structured (hunt -> calibrate confidence -> exclude non-issues -> emit JSON) with an explicit 'what you don't flag' checkpoint; it is not a destructive/batch operation so no validation feedback loop is required, keeping it above the cap.

4 / 5

Progressive Disclosure

A simple under-50-line skill with no external references needed; content is organized into well-labeled sections (what to hunt, confidence, exclusions, output), so the simple-skill exception applies and structure is clean.

5 / 5

Total

18

/

20

Passed

Description

56%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 specific and names a clear niche, but it omits any explicit 'Use when...' trigger guidance, which caps completeness at 3. Trigger-term coverage is adequate but lacks the natural phrases users would actually say.

Suggestions

Add an explicit trigger clause, e.g. 'Use when reviewing code for correctness bugs, logic errors, or edge cases.'

Include natural-language synonyms users would say, such as 'review my code', 'find bugs', or 'check for logic errors'.

Clarify how it differs from sibling reviewers (e.g. 'focuses on correctness, not performance or style') to reduce overlap risk.

DimensionReasoningScore

Specificity

Lists several concrete review categories -- 'logic errors, edge cases, state management bugs, error propagation failures, and intent-vs-implementation mismatches' -- with minor gaps in coverage breadth.

4 / 5

Completeness

Clearly answers 'what' (reviews code for specific bug classes) but provides no explicit 'Use when...' clause; 'Always-on' weakly implies triggering without stating when Claude should invoke it, capping completeness at 3 per the rubric.

3 / 5

Trigger Term Quality

Contains relevant terms like 'code-review', 'logic errors', and 'bugs', but lacks the natural synonyms a user would actually say ('review my code', 'find bugs', 'check correctness') and no file/extension triggers.

3 / 5

Distinctiveness Conflict Risk

The correctness-reviewer niche is mostly distinct from performance or style reviewers, though 'code-review persona' has some overlap risk with other review-focused skills.

4 / 5

Total

14

/

20

Passed

Validation

81%

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

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

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

Warning

Total

13

/

16

Passed

Repository
udecode/plate
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.