monitoring-database-transactions

Monitor 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".

Quality

65%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/database/database-transaction-monitor/skills/monitoring-database-transactions/SKILL.md

Quality

Content

80%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable and token-efficient, with concrete multi-database SQL and specific thresholds throughout. Its main gaps are the missing validation feedback loop around destructive remediation and the failure to surface the bundled scripts as one-level-deep references.

Suggestions

Add a validation/verification checkpoint around step 9's session termination (e.g., confirm pid, log termination, verify alert clears) to form a feedback loop.

Link the bundled scripts from the Instructions or Output section (e.g. 'See scripts/rollback_analyzer.py') so the bundle is discoverable rather than orphaned.

Consider moving the error-handling table and narrative examples into a reference file to keep SKILL.md as a tighter overview.

Dimension	Reasoning	Score
Conciseness	The body is dense and lean: every section delivers concrete SQL, specific thresholds, or actionable guidance with no padding or explanations of concepts Claude already knows.	3 / 3
Actionability	It provides fully executable, copy-paste-ready SQL for PostgreSQL, MySQL, and MongoDB, with specific thresholds (30s, 5min, 60s) and concrete remediation commands like pg_terminate_backend and KILL connection_id.	3 / 3
Workflow Clarity	The ten steps are clearly sequenced, but step 9 performs destructive session termination with no validation checkpoint or validate-fix-retry feedback loop, which the rubric caps at 2 for database operations.	2 / 3
Progressive Disclosure	The body is well-sectioned but monolithic, keeping all SQL, error handling, and examples inline, and it never references the bundled scripts/ files (transaction_monitor.py, lock_detector.py, rollback_analyzer.py), leaving them orphaned.	2 / 3
	Total	10 / 12 Passed

Description

50%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description has an explicit trigger clause and names a domain, but is awkwardly phrased, padded with buzzwords, and conspicuously omits the database-transaction focus that defines the skill. This vagueness weakens specificity, completeness, and distinctiveness alike.

Suggestions

Lead with the concrete capability, e.g. 'Detect long-running queries, lock contention, and idle-in-transaction sessions across PostgreSQL, MySQL, and MongoDB.'

Replace 'comprehensive guidance and automation' with specific actions such as alerting on thresholds and terminating stale sessions.

Add database/transaction trigger terms (e.g. 'database locks', 'idle in transaction', 'long-running queries') to reduce overlap with generic monitoring skills.

Dimension	Reasoning	Score
Specificity	It names the monitoring/observability domain and a couple of actions ('health monitoring and alerting'), but pads with vague fluff ('comprehensive guidance and automation') rather than listing concrete capabilities like detecting long-running queries or lock contention.	2 / 3
Completeness	It provides explicit trigger guidance ('Trigger with phrases like...') and a what-statement, but the what is weak ('provides health monitoring and alerting') and notably never mentions databases or transactions, so it does not clearly answer both what and when.	2 / 3
Trigger Term Quality	It offers three natural phrases ('monitor system health', 'set up alerts', 'track metrics') a user might say, but the set is thin and generic with no common variations, and 'monitor' repeats the domain rather than enriching it.	2 / 3
Distinctiveness Conflict Risk	The description describes generic 'monitoring and observability' without mentioning databases or transactions, so it could overlap with many monitoring skills despite the database-specific skill name.	2 / 3
	Total	8 / 12 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Path: plugins/database/database-transaction-monitor/skills/monitoring-database-transactions/SKILL.md
Commit: bddba3c

Reviewed: about 7 hours ago

Table of Contents

Discovery Implementation Validation

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.