detecting-database-deadlocks

Quick Review

The skill has reasonable structure and references scripts for deadlock detection, but the SKILL.md is filled with generic boilerplate text that doesn't explain deadlock-specific concepts, workflows, or how to use the referenced Python scripts. The description lacks clarity on what 'detect', 'resolve', and 'prevent' deadlocks actually means in practice. While scripts exist (analyze_deadlocks.py, resolve_deadlock.py, simulate_deadlock.py), the main documentation doesn't explain their purpose, parameters, or integration. The 5-step process is too generic and could apply to any backend task. For novelty, basic deadlock detection can often be done with standard database queries, though automation and analysis scripts add some value. To improve: replace generic text with deadlock-specific guidance (e.g., how to read database deadlock logs, common deadlock patterns, when to use each script, database-specific commands for PostgreSQL/MySQL/MongoDB).