Skip to content
TrustedSkillsbeta
Back to all skills

Database Query Optimization

Checked
aj-geddes·vlatest·database·MIT

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

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 database-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.

Scanned
7 files, 283 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 raw SQL queries and generate optimized versions that improve execution speed and resource efficiency. It specifically targets performance bottlenecks by suggesting structural changes to the query logic itself.

When to use it

  • Slow reporting dashboards: When data visualizations time out due to complex aggregation queries on large datasets.
  • High-latency APIs: To reduce response times for backend services fetching extensive user records or transaction logs.
  • Cost reduction: To minimize compute expenses in cloud databases by eliminating unnecessary full table scans.
  • Pre-production tuning: Before deploying heavy data migrations or batch processing jobs to ensure stability.

Key capabilities

  • Identifies inefficient indexing strategies within complex joins and subqueries.
  • Suggests specific SQL syntax improvements for better execution plans.
  • Analyzes query patterns to recommend partitioning or materialized views.
  • Detects redundant operations like repeated table scans or unfiltered data retrieval.

Example prompts

  • "Analyze this SQL query fetching last year's sales data and suggest optimizations for a PostgreSQL database."
  • "Rewrite this inefficient join operation to reduce execution time on a 10 million row dataset."
  • "Identify potential performance bottlenecks in this stored procedure used for nightly reporting."

Tips & gotchas

Ensure your AI agent has access to the specific database schema and statistics, as optimization strategies vary significantly between engines like MySQL, PostgreSQL, and SQL Server. Always test generated queries in a staging environment before applying them to production data to prevent accidental data loss or locking issues.