monitoring-database-transactions

Quick Review

This skill suffers from severe generic templating issues. While the structure is clear and organized, the content is almost entirely boilerplate that could apply to any DevOps task. The description mentions 'database transaction monitoring' but provides no specific guidance on what metrics to collect (transaction latency, deadlocks, throughput), which queries to monitor, how to set thresholds, or database-specific monitoring approaches (PostgreSQL vs MySQL vs MongoDB). The 5-step process (Assess, Design, Implement, Validate, Deploy) is a standard SDLC that doesn't provide actionable task knowledge for actually monitoring database transactions. A CLI agent would struggle to invoke this skill effectively because it lacks concrete parameters, monitoring tools, query examples, or specific alerting configurations. The skill provides minimal value over a general DevOps agent with basic knowledge, as it contains no specialized database monitoring expertise or automation scripts.