Implement comprehensive database monitoring for performance analysis, health checks, and proactive alerting. Covers metrics collection, analysis, and troubleshooting strategies.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versiondatabase-monitoringExecute the skills CLI command in your project's root directory to begin installation:
Fetches database-monitoring from aj-geddes/useful-ai-prompts and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate database-monitoring. Access via /database-monitoring in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
162
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
162
stars
Implement comprehensive database monitoring for performance analysis, health checks, and proactive alerting. Covers metrics collection, analysis, and troubleshooting strategies.
Minimal working example:
-- View current connections
SELECT
pid,
usename,
application_name,
client_addr,
state,
query_start,
state_change
FROM pg_stat_activity
WHERE state != 'idle'
ORDER BY query_start DESC;
-- Count connections per database
SELECT
datname,
COUNT(*) as connection_count,
MAX(EXTRACT(EPOCH FROM (NOW() - query_start))) as max_query_duration_sec
FROM pg_stat_activity
GROUP BY datname;
-- Find idle transactions
SELECT
pid,
usename,
// ... (see reference guides for full implementation)
Detailed implementations in the references/ directory:
| Guide | Contents |
|---|---|
| Connection Monitoring | Connection Monitoring |
| Query Performance Monitoring | Query Performance Monitoring |
| Table & Index Monitoring | Table & Index Monitoring |
| Performance Schema | Performance Schema |
| InnoDB Monitoring | InnoDB Monitoring |
| PostgreSQL Monitoring Setup | PostgreSQL Monitoring Setup |
| Automated Monitoring Dashboard | Automated Monitoring Dashboard |
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
database-monitoring reduced setup friction for our internal harness; good balance of opinion and flexibility.
Keeps context tight: database-monitoring is the kind of skill you can hand to a new teammate without a long onboarding doc.
database-monitoring has been reliable in day-to-day use. Documentation quality is above average for community skills.
Keeps context tight: database-monitoring is the kind of skill you can hand to a new teammate without a long onboarding doc.
database-monitoring fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
I recommend database-monitoring for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
database-monitoring has been reliable in day-to-day use. Documentation quality is above average for community skills.
Solid pick for teams standardizing on skills: database-monitoring is focused, and the summary matches what you get after install.
database-monitoring is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
We added database-monitoring from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
showing 1-10 of 47