Skip to content
TrustedSkillsbeta
Back to all skills

Database Performance

Checked
aaronontheweb·vlatest·database·MIT

Helps with database, performance 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 aaronontheweb/dotnet-skills --skill database-performance -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

aaronontheweb

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 aaronontheweb/dotnet-skills at e426ed93a9.

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

Commit
e426ed93a9
Manifest
skills/database-performance/SKILL.md
Scanned
1 file, 470 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

The database-performance skill enables AI agents to optimize query execution plans, manage connection pools, and tune indexing strategies for relational databases. It helps identify bottlenecks in data retrieval and ensures efficient resource utilization during high-load scenarios.

When to use it

  • Diagnosing slow query performance in production environments.
  • Tuning index configurations to reduce disk I/O operations.
  • Managing database connection limits to prevent timeouts.
  • Analyzing execution plans for complex joins or aggregations.

Key capabilities

  • Query plan analysis and optimization suggestions.
  • Index creation, removal, and performance impact assessment.
  • Connection pool monitoring and configuration tuning.
  • Resource usage tracking (CPU, memory, I/O) per query.
  • Automated recommendations for schema adjustments.

Example prompts

  • "Analyze this SQL query and suggest optimizations for better performance."
  • "Identify missing indexes that could speed up these frequently run reports."
  • "Tune the connection pool settings based on current load patterns."

Tips & gotchas

Ensure you have appropriate database access permissions before running optimization commands. Always test changes in a staging environment first to avoid unintended side effects on live data.