Skip to content
TrustedSkillsbeta
Back to all skills

Sql Query Optimization

Checked
aj-geddes·vlatest·database·MIT

Helps with querying, optimization as part of working with databases and data persistence workflows.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add aj-geddes/useful-ai-prompts --skill sql-query-optimization -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

aj-geddes

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.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

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 aj-geddes/useful-ai-prompts at 3f5182cfd7.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
3f5182cfd7
Manifest
skills/sql-query-optimization/SKILL.md
Scanned
7 files, 224 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill enables AI agents to analyze SQL queries for performance bottlenecks and generate optimized versions that reduce execution time. It specifically targets inefficient patterns like missing indexes, suboptimal joins, and unnecessary data retrieval.

When to use it

  • Slow reports: When dashboard loads exceed acceptable thresholds due to complex database queries.
  • High-volume transactions: Before deploying batch jobs or ETL processes on large datasets.
  • Cost reduction: To minimize cloud database compute costs by reducing query runtime.
  • Legacy modernization: Refactoring old, unoptimized SQL codebases for better maintainability.

Key capabilities

  • Identifies missing indexes that cause full table scans
  • Suggests optimal join strategies and orderings
  • Detects redundant columns in SELECT statements
  • Flags inefficient subqueries that can be rewritten as joins
  • Recommends appropriate index creation or removal

Example prompts

"Analyze this SQL query for performance issues: [paste query]" "Optimize this slow reporting query for a 10 million row table" "Suggest index improvements for this frequently used join operation"

Tips & gotchas

Ensure you provide the full query context and relevant schema details (table sizes, existing indexes) for accurate recommendations. Some optimizations may require database-specific syntax adjustments depending on your SQL dialect.