Skip to content
TrustedSkillsbeta
Back to all skills

Database Optimizer

Checked
jeffallan·vlatest·database·MIT

Analyzes and suggests SQL query optimizations and index improvements to boost database performance.

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 jeffallan/claude-skills --skill database-optimizer -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

jeffallan

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 jeffallan/claude-skills at 1be15d8064.

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

Commit
1be15d8064
Manifest
skills/database-optimizer/SKILL.md
Scanned
6 files, 1,952 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

The database-optimizer skill helps improve the performance of databases by analyzing queries, suggesting index optimizations, and identifying inefficient operations. It can review SQL statements and recommend changes to enhance speed and reduce resource usage.

When to use it

  • You're experiencing slow query execution times in your database.
  • You want to optimize a complex SQL query for better performance.
  • Your application is using excessive resources due to inefficient database operations.
  • You need guidance on how to structure queries or indexes for improved efficiency.

Key capabilities

  • Analyzes SQL queries for optimization opportunities
  • Suggests index creation and modification strategies
  • Identifies redundant or inefficient operations in queries
  • Provides performance improvement recommendations

Example prompts

  • "Optimize this SQL query: SELECT * FROM users WHERE created_at > '2023-01-01';"
  • "What indexes should I add to improve the speed of this table?"
  • "Review and suggest improvements for this database schema."

Tips & gotchas

  • Ensure you have access to your database's query logs or execution plans for accurate analysis.
  • Some optimizations may require changes to your application logic or data structure, so consider testing in a development environment first.