704-technologies-sql — Claude Code skill: SQL and install
The 704-technologies-sql skill guides schema design, SQL queries, indexes, and migrations without tying the advice to a Java framework. Use it for database reviews and changes.
Apache-2.0 227 installs ★ 465 updated 2026-10-21
npx skills add jabrena/plinth --skill 704-technologies-sql -a claude-codeWhat 704-technologies-sql does
This skill covers naming for tables, columns, indexes, constraints, views, triggers, and routines. It also guides relational design around keys, constraints, timestamps, soft deletes, normalization, and database-specific types.
For queries, it focuses on readable structure, explicit column lists, joins, CTEs, bind parameters, and execution-plan checks. The workflow reads references/704-technologies-sql.md, inspects schemas, migrations, tests, queries, and database configuration, then reports verification results. Security, transactions, testing, monitoring, and index lifecycle are part of the review.
The scope stays at the SQL and database-design layer. If the database dialect, migration tool, or production constraint changes the recommendation, clarification is required before SQL is edited; Spring JDBC, Quarkus JDBC, and Micronaut JDBC work belongs to their matching skills.
What it helps with
- review SQL schemas and migrations
- rewrite a query for clarity and plan review
- design relational tables with suitable indexes
- check SQL injection and transaction risks
- validate migration and database tests
Example prompts for the agent
- Review this project’s SQL schema and migrations for the target database dialect.
- Improve this query’s readability and performance, then inspect its execution plan.
- Design relational tables and indexes for this data model, including portability risks.
How to install 704-technologies-sql
1Skills CLI (Vercel)
npx skills add jabrena/plinth --skill 704-technologies-sql -a claude-code2Manually: put the files in place
~/.claude/skills/704-technologies-sql/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/704-technologies-sql/
1Skills CLI (Vercel)
npx skills add jabrena/plinth --skill 704-technologies-sql -a codex2Manually: put the files in place
.agents/skills/704-technologies-sql/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add jabrena/plinth --skill 704-technologies-sql -a cursor2Manually: put the files in place
.cursor/skills/704-technologies-sql/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install jabrena/plinth skills/704-technologies-sql2Manually: put the files in place
.github/skills/704-technologies-sql/SKILL.md1Skills CLI (Vercel)
npx skills add jabrena/plinth --skill 704-technologies-sql -a gemini-cli2Platform CLI
gemini skills install https://github.com/jabrena/plinth --path skills/704-technologies-sqlManually: put the files in place
.devin/skills/704-technologies-sql/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add jabrena/plinth --skill 704-technologies-sql -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about 704-technologies-sql
How do I install 704-technologies-sql in Claude Code?
Run npx skills add jabrena/plinth --skill 704-technologies-sql -a claude-code, then check ~/.claude/skills/704-technologies-sql/SKILL.md.
What does 704-technologies-sql do?
It guides relational schema design, readable SQL, index choices, and reviews of database security, transactions, migrations, testing, and monitoring.
What must be confirmed before changing SQL?
Confirm the database engine, migration tool, and operational constraints when they affect the recommendation. Java integration for Spring JDBC, Quarkus JDBC, or Micronaut JDBC is handled by matching skills.
Source text
SKILL.md · Apache-2.0
--- name: 704-technologies-sql description: 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 Plinth Toolkit license: Apache-2.0 metadata: author: Juan Antonio Breña Moral version: 0.19.0 --- # SQL best practices Help teams create maintainable, secure, and performant **SQL** for Java applications across relational database engines. **What is covered in this Skill?** - Naming conventions for tables, columns, indexes, constraints, views, triggers, and routines - Relational table design: keys, constraints, timestamps, soft deletes, normalization, and dialect-aware data types - Query writing: readable formatting, explicit column lists, joins, CTEs, bind parameters, and execution-plan review - Index strategy: foreign keys, filter/sort paths, composite indexes, over-indexing risks, and index lifecycle - Security, transactions, migrations, testing, and monitoring practices for production database work **Scope:** Framework-agnostic SQL quality. For Java data-access APIs, defer to the matching JDBC, Spring Data JDBC, Panache, or Micronaut Data skill. ## Constraints Keep recommendations at the SQL and database-design layer unless the user explicitly asks for Java framework integration. After editing this repository's XML sources, regenerate skills and verify the build. - **MANDATORY**: Run `./mvnw compile` or `mvn compile` before proposing Java or Maven changes in the same change set - **SQL INJECTION**: Never concatenate untrusted input into SQL strings; use bind parameters through the application's data-access API - **DIALECTS**: Call out database-specific syntax and portability trade-offs when using PostgreSQL, MySQL, Oracle, SQL Server, H2, or another engine - **FRAMEWORK**: Defer Spring JDBC to `@311-frameworks-spring-jdbc`, Quarkus JDBC to `@411-frameworks-quarkus-jdbc`, Micronaut JDBC to `@511-frameworks-micronaut-jdbc`, and framework-specific migrations to the matching Flyway skill - **VERIFY**: Run `./mvnw clean verify` or `mvn clean verify` before promoting changes - **EDGE CASE**: If the target database dialect, migration tool, or production constraint is missing and affects the recommendation, ask a clarifying question before editing SQL - **EDGE CASE**: If requested changes conflict with data safety, backwards compatibility, or zero-downtime deployment constraints, explain the trade-off and ask for confirmation ## When to use this skill - Review SQL schema or migrations - Improve SQL query performance and readability - Design relational tables and indexes - Review database transaction, security, or monitoring practices - Apply SQL best practices to database DDL or DML ## Workflow 1. **Read reference and assess database context** Read `references/704-technologies-sql.md` and inspect current schema, migrations, SQL queries, tests, and database configuration before proposing changes. 2. **Identify dialect and operational constraints** Confirm the target database engine, migration tool, data volume expectations, availability requirements, and compatibility constraints that shape the SQL design. 3. **Apply SQL-aligned changes** Implement or refactor SQL artifacts following the reference patterns and project conventions, keeping Java framework integration out of scope unless explicitly requested. 4. **Run verification and report results** Execute appropriate build, migration, SQL validation, and test checks; summarize what changed, what was verified, and any remaining database risks. ## Reference For detailed guidance, examples, and constraints, see [references/704-technologies-sql.md](references/704-technologies-sql.md).
© Juan Antonio Breña Moral · Apache-2.0 · jabrena/plinth