detecting-database-deadlocks

Quick Review

The skill has reasonable structure and references useful scripts (analyze_deadlocks.py, resolve_deadlock.py, simulate_deadlock.py), but suffers from a critical mismatch: the SKILL.md content is a generic template ('Database Deadlock Detector') that doesn't provide specific deadlock detection guidance. The description mentions triggering phrases and deadlock workflows, yet the implementation steps are boilerplate (Assess, Design, Implement, Validate, Deploy) without deadlock-specific knowledge like identifying wait-for graphs, lock ordering, timeout strategies, or database-specific deadlock queries. While the scripts directory suggests concrete tools exist, the main documentation fails to explain deadlock concepts, detection methods, or resolution strategies that would enable a CLI agent to effectively use this skill. The novelty is low because deadlock detection via SQL queries or monitoring tools is straightforward for experienced agents. To improve: replace generic steps with deadlock-specific workflows (capture lock hierarchies, analyze transaction logs, implement retry logic), provide database-specific query examples, and explain when to use each referenced script.