Db Performance Watchlist
CheckedMonitors database performance metrics, flags anomalies, and creates a watchlist for proactive optimization by Patricio.
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 patricio0312rev/skills --skill db-performance-watchlist -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
patricio0312rev
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 patricio0312rev/skills at 79ea6af485.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 79ea6af485
- Scanned
- 1 file, 408 lines
About this skill
What it does
The Db Performance Watchlist skill monitors key performance metrics for databases, specifically PostgreSQL. It identifies slow-running queries and tracks connection pool usage to help prevent regressions and proactively optimize database performance. The tool provides insights into query duration, resource utilization (CPU, memory, disk), cache hit rates, index usage, and connection pool statistics.
When to use it
- You suspect your database is experiencing performance slowdowns or regressions.
- You want to identify queries that are taking an unusually long time to execute.
- You need to monitor the health and utilization of your database's connection pool.
- You’re proactively seeking ways to optimize database resource usage.
- You want to track cache performance and identify potential index improvements.
Key capabilities
- Slow Query Detection: Identifies queries exceeding a configurable threshold (default 100ms) using PostgreSQL's
pg_stat_statements. - Connection Pool Monitoring: Tracks active, idle, total connections, and maximum connection limits within the database.
- Key Performance Metric Tracking: Monitors metrics including query performance, resource usage (CPU, memory, disk I/O), query statistics (selects, inserts, updates, deletes per second), cache hit rate, and index usage.
- Reporting: Provides detailed reports on slow queries, including duration, call count, average duration, maximum duration, and percentage of total time spent.
Example prompts
- "Run the database performance watchlist to check for slow queries."
- "Show me the current connection pool statistics for the database."
- "What are the top 20 slowest queries running in the last hour?"
- “Check if there are any unused indexes.”
Tips & gotchas
- This skill is designed specifically for PostgreSQL databases.
- The slow query detection feature requires
log_min_duration_statementto be configured within the database (the script will attempt this). - Ensure the agent has appropriate permissions to query system views like
pg_stat_statementsandpg_settings.