monitoring-database-transactions
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill monitoring-database-transactionsMonitor use when you need to work with monitoring and observability. This skill provides health monitoring and alerting with comprehensive guidance and automation. Trigger with phrases like "monitor system health", "set up alerts", or "track metrics".
Validation
81%| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 13 / 16 Passed | |
Implementation
20%This skill is a generic template with no database transaction monitoring-specific content. It reads like boilerplate project management guidance that could apply to any technical task. There are no concrete examples of monitoring queries, alert configurations, metric definitions, or actual database transaction monitoring code.
Suggestions
Add concrete, executable examples of database transaction monitoring queries (e.g., SQL for detecting long-running transactions, deadlocks, or transaction throughput)
Include specific alert threshold configurations and monitoring tool setup (e.g., Prometheus queries, Grafana dashboard JSON, or specific CLI commands)
Replace generic steps like 'Review current configuration' with specific actions like 'Query pg_stat_activity for active transactions older than 5 minutes'
Remove all generic advice Claude already knows (permission checks, network troubleshooting basics) and focus only on database transaction monitoring-specific guidance
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with generic boilerplate that applies to any task. Explains obvious concepts like 'verify credentials' and 'check network connectivity' that Claude already knows. No database transaction monitoring-specific content. | 1 / 3 |
Actionability | Entirely abstract and vague with no concrete code, commands, or specific examples. Instructions like 'Review current configuration' and 'Execute implementation' provide no executable guidance for database transaction monitoring. | 1 / 3 |
Workflow Clarity | Steps are numbered and sequenced, but they're generic project management phases rather than database monitoring-specific workflows. No concrete validation checkpoints or feedback loops for actual monitoring tasks. | 2 / 3 |
Progressive Disclosure | References external files in Resources section, but the main content is a monolithic wall of generic text. The referenced files use placeholder paths that may not exist, and the structure doesn't help navigate to useful content. | 2 / 3 |
Total | 6 / 12 Passed |
Activation
67%The description adequately covers the 'what' and 'when' with explicit trigger phrases, which is its main strength. However, it lacks specificity in concrete actions and could include more natural keyword variations that users commonly use when discussing monitoring and observability tools.
Suggestions
Add more specific concrete actions like 'configure alerting thresholds', 'create monitoring dashboards', 'integrate with Prometheus/Grafana', or 'set up health checks'
Expand trigger terms to include common variations like 'observability', 'uptime monitoring', 'logging', 'APM', or specific tool names users might mention
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (monitoring/observability) and mentions some actions ('health monitoring', 'alerting', 'track metrics'), but lacks concrete specific actions like 'configure dashboards', 'set threshold alerts', or 'integrate with Prometheus'. | 2 / 3 |
Completeness | Explicitly answers both what ('health monitoring and alerting with comprehensive guidance and automation') and when ('Trigger with phrases like...' provides clear usage triggers), meeting the requirement for explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes some natural trigger phrases ('monitor system health', 'set up alerts', 'track metrics') but missing common variations users might say like 'observability', 'logging', 'uptime', 'Grafana', 'Datadog', or 'performance monitoring'. | 2 / 3 |
Distinctiveness Conflict Risk | Somewhat specific to monitoring/observability domain, but 'track metrics' and 'alerting' could overlap with analytics, logging, or DevOps skills. Could benefit from more specific tool names or use cases. | 2 / 3 |
Total | 9 / 12 Passed |
Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.