CtrlK
BlogDocsLog inGet started
Tessl Logo

code-reviewer

Use when reviewing Spring Boot 4 / Java 17+ code with concrete files or diffs — pull requests, modules, or pasted Java/Spring sources — for migration risks, architecture boundary leaks, JSpecify null-safety gaps, security flaws, performance regressions, or Spring Data pitfalls. Not for Kotlin-only code, non-Spring frameworks, or generic review advice without code context.

92

2.10x
Quality

89%

Does it follow best practices?

Impact

99%

2.10x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

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

A well-structured, token-efficient review skill with a clear multi-pass workflow and excellent progressive disclosure verified against the real reference bundle. Main gaps are minor: guidance leans on check-prompts over executable commands and lacks explicit validation feedback loops.

Suggestions

Add an explicit verification checkpoint after Step 1 (e.g. 'Confirm pom.xml/build.gradle Java and Boot versions before proceeding to passes') to turn the scope step into a true validate-and-proceed loop.

For the highest-impact passes (migration, data access), include one concrete before/after code snippet or command so findings are copy-paste ready rather than prompt-only.

State the 'Always cite file paths and line numbers' rule as a checkpoint in the report-format step so it functions as a validation gate rather than a standalone rule.

DimensionReasoningScore

Conciseness

Lean bulleted passes with no conceptual padding (no explanations of what Spring, JPA, or null-safety are); every line assumes Claude's competence and earns its place.

5 / 5

Actionability

Specific, verifiable guidance tied to real artifacts (spring.mvc.apiversion.*, @ConcurrencyLimit, RestTestClient vs TestRestTemplate, Jackson 3), but guidance is mostly check-prompts rather than copy-paste commands.

4 / 5

Workflow Clarity

Clearly sequenced scope-confirm → load-refs → passes A–F workflow with named review modes, but explicit validation/feedback checkpoints (e.g. verify build files, confirm line citations) are only implied rather than looped.

4 / 5

Progressive Disclosure

SKILL.md is a concise overview; all eight reference paths in the mapping table and modes resolve to real files in ./references/, one level deep and clearly signaled, with explicit sibling-skill escalation.

5 / 5

Total

18

/

20

Passed

Description

92%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, specific description with clear trigger phrases, comprehensive capability coverage, and explicit negative boundaries that distinguish it from sibling skills. The only minor gap is missing a few natural synonym/extension trigger terms.

DimensionReasoningScore

Specificity

Enumerates concrete review actions across six explicit risk categories (migration risks, architecture boundary leaks, JSpecify null-safety gaps, security flaws, performance regressions, Spring Data pitfalls), matching the comprehensive-coverage anchor.

5 / 5

Completeness

Explicitly answers both what (reviewing Spring Boot 4 / Java 17+ code for named risk categories) and when (Use when reviewing concrete files, diffs, or PRs), plus a concrete exclusion clause for when not to use it.

5 / 5

Trigger Term Quality

Strong natural terms users would say (pull requests, diffs, migration risks, security flaws, Spring Data), but a few common synonyms/extensions are absent, placing it just below full synonym saturation.

4 / 5

Distinctiveness Conflict Risk

Narrow SB4/Java 17+ niche with explicit exclusions (Kotlin-only, non-Spring frameworks, generic coaching) minimizes conflict with sibling skills.

5 / 5

Total

19

/

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
a-pavithraa/springboot-skills-marketplace
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.