CtrlK
BlogDocsLog inGet started
Tessl Logo

code-review

Code review practices with technical rigor and verification gates. Use for receiving feedback, requesting code-reviewer subagent reviews, or preventing false completion claims in pull requests.

94

1.06x
Quality

93%

Does it follow best practices?

Impact

94%

1.06x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

100%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.

An exemplar content body: lean, actionable, and well-structured with explicit verification gates and one-level-deep references to real bundle files. No significant weaknesses across any dimension.

DimensionReasoningScore

Conciseness

Lean and efficient throughout: terse bullets, a compact decision tree, and copy-paste commands, with no over-explanation of concepts Claude already knows.

5 / 5

Actionability

Provides concrete, executable guidance including git SHA commands, dispatch instructions, and runnable verification commands (bun test, bun run build, etc.) covering the common cases.

5 / 5

Workflow Clarity

Multi-step processes are explicitly sequenced (READ→UNDERSTAND→VERIFY→EVALUATE→RESPOND→IMPLEMENT; IDENTIFY→RUN→READ→VERIFY→THEN claim) with explicit validation checkpoints and error-recovery feedback loops.

5 / 5

Progressive Disclosure

Clear overview with three well-signaled, one-level-deep references to real files (code-review-reception.md, requesting-code-review.md, verification-before-completion.md); content is appropriately split and easy to navigate.

5 / 5

Total

20

/

20

Passed

Description

87%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.

A strong, concise description that clearly states both capabilities and concrete usage triggers. It is distinct and actionable, with only minor synonym/keyword coverage gaps.

Suggestions

Add common synonyms like 'code review' or 'PR review' to broaden natural trigger-term coverage.

Consider mentioning review comments explicitly, since 'receiving feedback' alone may not match how users phrase review-comment requests.

DimensionReasoningScore

Specificity

Names the domain and lists several concrete practices ('receiving feedback, requesting code-reviewer subagent reviews, or preventing false completion claims'), with only minor gaps in coverage.

4 / 5

Completeness

Explicitly answers both what ('Code review practices with technical rigor and verification gates') and when ('Use for receiving feedback, requesting code-reviewer subagent reviews, or preventing false completion claims') with concrete triggers.

5 / 5

Trigger Term Quality

Includes natural trigger phrases users would say ('receiving feedback', 'code-reviewer reviews', 'pull requests') but misses common synonyms like 'code review' or 'PR review'.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (technical rigor + verification gates + subagent reviews) with distinct triggers and minimal overlap risk against other skills.

5 / 5

Total

18

/

20

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
secondsky/claude-skills
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.