CtrlK
BlogDocsLog inGet started
Tessl Logo

312-frameworks-spring-data-jdbc

Use when you need to use Spring Data JDBC with Java records — including entity design with records, repository pattern, immutable updates, aggregate relationships, custom queries, transaction management, and avoiding N+1 problems. This should trigger for requests such as Review Java code for Spring Data JDBC; Apply best practices for Spring Data JDBC in Java code; Model Spring Data JDBC aggregates with Java records; Review Spring Data JDBC repositories and aggregate boundaries; Improve optimistic locking or domain events in Spring Data JDBC. Part of Plinth Toolkit

67

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

70%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured overview with clear validation checkpoints and clean progressive disclosure to one reference file. It is held back by redundancy with the description and by implementation guidance that is abstract rather than concrete.

Suggestions

Remove the 'When to use this skill' section (and trim the 'What is covered' list) since both duplicate the frontmatter description, keeping only the overview bullets that add information beyond the description.

Add one or two concrete, copy-pasteable code snippets for the most common task (e.g., a record entity with @Id/@Table and a repository interface) instead of deferring all implementation detail to the reference file.

In workflow step 3, replace 'following the reference patterns and project conventions' with a specific, actionable instruction naming the pattern to apply or the reference section to consult.

DimensionReasoningScore

Conciseness

The body is lean and avoids explaining concepts Claude already knows, but the 'What is covered in this Skill?' bullet list and the 'When to use this skill' section largely duplicate the description's capabilities and triggers, so it could be tightened. It is not a 3 because of that redundancy.

2 / 3

Actionability

It provides concrete build commands ('./mvnw compile or mvn compile', './mvnw clean verify or mvn clean verify') but the core implementation guidance is abstract and deferred ('Implement or refactor configuration/code following the reference patterns and project conventions'), so concrete detail is incomplete.

2 / 3

Workflow Clarity

The four-step workflow is clearly sequenced and the Constraints section supplies explicit validation checkpoints with a feedback loop ('MANDATORY: Run mvn compile before', 'SAFETY: If compilation fails, stop immediately', 'VERIFY: Run mvn clean verify after').

3 / 3

Progressive Disclosure

The body is a concise overview that points to a single one-level-deep reference (references/312-frameworks-spring-data-jdbc.md), clearly signaled in both the Workflow and Reference sections; the referenced file exists.

3 / 3

Total

10

/

12

Passed

Description

90%

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 explicit trigger phrasings and a clear niche. The only issue is second-person voice ('Use when you need to'), which the rubric penalizes on specificity.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions ('entity design with records, repository pattern, immutable updates, aggregate relationships, custom queries, transaction management, and avoiding N+1 problems'), which would normally be a 3, but it uses second person ('Use when you need to use Spring Data JDBC'), which the rubric penalizes by reducing specificity by 1.

2 / 3

Completeness

It explicitly answers both what (the enumerated capabilities) and when ('This should trigger for requests such as...'), matching the anchor for a full what-and-when answer with explicit triggers.

3 / 3

Trigger Term Quality

It gives good coverage of natural request phrasings users would say ('Review Java code for Spring Data JDBC; Apply best practices...; Model Spring Data JDBC aggregates with Java records; Review Spring Data JDBC repositories and aggregate boundaries; Improve optimistic locking or domain events').

3 / 3

Distinctiveness Conflict Risk

The niche is narrow and specific — Spring Data JDBC with Java records — with triggers unlikely to fire for unrelated skills, matching the clear-niche anchor.

3 / 3

Total

11

/

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
jabrena/plinth
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.