Sql Best Practices
CheckedProvides best practices guidance and assistance for working with databases and data persistence.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add mindrally/skills --skill sql-best-practices -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
mindrally
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned mindrally/skills at 7682ca7771.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 7682ca7771
- Manifest
- sql-best-practices/SKILL.md
- Scanned
- 1 file, 200 lines
About this skill
What it does
This skill provides guidance and assistance for writing SQL code that adheres to best practices. It focuses on improving query readability, performance, security, and data integrity through consistent formatting, optimized indexing, and secure coding techniques. The skill offers advice on structuring queries, selecting columns effectively, filtering data efficiently, and using joins appropriately.
When to use it
- When you need help writing clear and readable SQL code for database interactions.
- When optimizing existing SQL queries for better performance.
- When ensuring your SQL code is secure against potential vulnerabilities like SQL injection.
- When working with complex queries that require documentation and explanation.
- To ensure consistent formatting and style across a codebase of SQL scripts.
Key capabilities
- Provides guidance on formatting and styling SQL code (uppercase keywords, newlines, aliases).
- Offers advice for optimizing query performance through indexing and avoiding functions on indexed columns.
- Emphasizes security best practices to prevent SQL injection using parameterized queries.
- Suggests appropriate use of transactions for data integrity.
- Promotes explicit JOIN syntax over implicit joins.
Example prompts
- "Can you review this SQL query for readability and suggest improvements?" (followed by providing the query)
- "How can I optimize this query to improve performance?" (followed by providing the query)
- "What are some best practices for preventing SQL injection in this code snippet?" (followed by providing a relevant code section)
Tips & gotchas
- The skill focuses on general SQL best practices and may not be specific to any particular database system.
- Pay attention to the formatting guidelines, as consistent style significantly improves readability.
- Remember to explicitly list required columns instead of using
SELECT *in production code.