704-technologies-sql

Use when you need framework-agnostic SQL guidance — schema naming, relational table design, query readability, indexes, transactions, database security, migrations, testing, and monitoring — without choosing Spring Boot, Quarkus, or Micronaut. This should trigger for requests such as Review SQL schema or migrations; Improve SQL query performance and readability; Design relational tables and indexes; Review database transaction, security, or monitoring practices. Part of cursor-rules-java project

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

85%

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

A well-organized, concise skill body with clear scope, explicit constraints, a verified workflow, and a single real one-level-deep reference. Its main gap is that the workflow steps lean on the reference for executable detail rather than showing concrete SQL examples inline.

Suggestions

Inline a minimal executable SQL example (e.g., a bind-parameter query or index DDL snippet) so the body provides copy-paste-ready guidance rather than deferring all detail to the reference.

In workflow step 3, replace 'Implement or refactor SQL artifacts following the reference patterns' with 1-2 concrete actions that name the specific reference subsections to consult for each task.

Add a short validation command or SQL linting step inside the workflow for non-Maven contexts (e.g., when no Java build is involved) so verification always has an executable checkpoint.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence: a tight scope statement, a bulleted constraint list, and a 4-step workflow with no padding or explanation of basic SQL concepts. Every section earns its place.	3 / 3
Actionability	Concrete commands appear (./mvnw compile, ./mvnw clean verify) and the reference file is named, but the workflow steps themselves are abstract directives ('Implement or refactor SQL artifacts following the reference patterns') rather than copy-paste-ready executable guidance, so it is not fully at the 3 anchor.	2 / 3
Workflow Clarity	A clearly numbered 4-step sequence with an explicit verification/reporting step (step 4) and MANDATORY/VERIFY/EDGE CASE checkpoints for risky database changes, satisfying the feedback-loop and validation anchor.	3 / 3
Progressive Disclosure	The body is a concise overview pointing to a single one-level-deep reference (references/704-technologies-sql.md) that exists on disk, clearly signaled via both a Workflow reference and a final Reference link, with no nested references.	3 / 3
	Total	11 / 12 Passed

Description

100%

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 that clearly states capabilities, includes explicit natural-language triggers, and draws a sharp boundary against related framework-specific skills. It uses third person throughout and avoids fluff.

Dimension	Reasoning	Score
Specificity	Lists many concrete actions: 'schema naming, relational table design, query readability, indexes, transactions, database security, migrations, testing, and monitoring', matching the anchor for multiple specific concrete actions.	3 / 3
Completeness	Explicitly answers both 'what' (the enumerated SQL capabilities) and 'when' via a clear 'Use when...' clause plus four explicit trigger examples, satisfying the highest anchor.	3 / 3
Trigger Term Quality	Embeds natural user phrasing ('Review SQL schema or migrations', 'Improve SQL query performance and readability', 'Design relational tables and indexes') that a user would actually say, giving good coverage of natural terms.	3 / 3
Distinctiveness Conflict Risk	The 'framework-agnostic SQL guidance... without choosing Spring Boot, Quarkus, or Micronaut' framing carves a clear niche and explicitly defers framework-specific work, making conflicts with sibling skills unlikely.	3 / 3
	Total	12 / 12 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: jabrena/cursor-rules-java
Commit: 86eb63d

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.