detecting-database-deadlocks
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill detecting-database-deadlocksProcess use when you need to work with deadlock detection. This skill provides deadlock detection and resolution with comprehensive guidance and automation. Trigger with phrases like "detect deadlocks", "resolve deadlocks", or "prevent deadlocks".
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
7%This skill is a generic template with 'database-deadlock-detector' substituted into placeholder text. It contains zero actual deadlock detection content - no SQL queries to find blocking sessions, no commands to identify lock waits, no database-specific guidance (PostgreSQL vs MySQL vs SQL Server), and no concrete resolution steps. The entire content could apply to any software task.
Suggestions
Add concrete SQL queries for detecting deadlocks (e.g., `SELECT * FROM pg_locks` for PostgreSQL, `SHOW ENGINE INNODB STATUS` for MySQL, `sys.dm_tran_locks` for SQL Server)
Include specific commands to identify and kill blocking sessions with executable examples
Replace generic 5-step process with deadlock-specific workflow: detect → analyze lock graph → identify victim → resolve → prevent recurrence
Add database-specific sections or clearly indicate which database system this targets, with actual connection and query examples
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with generic boilerplate that applies to any task. Contains no deadlock-specific content - just template text like 'Review current configuration' and 'Execute implementation' that Claude already knows. Every section is padded with obvious advice. | 1 / 3 |
Actionability | No concrete code, commands, or deadlock-specific guidance. Instructions like 'Assess Current State' and 'Design Solution' are abstract process descriptions, not executable steps. No SQL queries for detecting deadlocks, no specific database commands, no actual detection logic. | 1 / 3 |
Workflow Clarity | The 5-step workflow is a generic software development lifecycle, not a deadlock detection workflow. Missing actual deadlock-specific steps like querying lock tables, identifying blocking chains, or killing sessions. No validation checkpoints specific to deadlock resolution. | 1 / 3 |
Progressive Disclosure | References external files (templates, docs, examples) which is good structure, but the main content is a monolithic wall of generic text. The referenced files appear to be placeholders rather than real resources with actual deadlock detection content. | 2 / 3 |
Total | 5 / 12 Passed |
Activation
40%This description suffers from vague, buzzword-heavy language ('comprehensive guidance and automation') that fails to communicate concrete capabilities. While it includes explicit trigger phrases which is positive, the lack of specific actions (what does detection/resolution actually involve?) makes it difficult to understand the skill's value. The opening 'Process use when' appears to be a grammatical error.
Suggestions
Replace 'comprehensive guidance and automation' with specific actions like 'Analyzes thread dumps to identify circular dependencies, detects lock ordering violations, and generates resolution strategies'
Expand trigger terms to include natural user phrases like 'thread stuck', 'application hanging', 'lock contention', 'circular wait', 'concurrent access issues'
Fix the grammatical error in 'Process use when' - this appears malformed and should be rewritten for clarity
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'comprehensive guidance and automation' without listing concrete actions. It doesn't specify what deadlock detection actually does (e.g., analyze thread dumps, identify circular dependencies, generate resolution strategies). | 1 / 3 |
Completeness | Has explicit trigger phrases which partially addresses 'when', but the 'what' is extremely weak - 'comprehensive guidance and automation' is meaningless fluff. The description fails to explain what the skill actually does. | 2 / 3 |
Trigger Term Quality | Includes some relevant trigger phrases ('detect deadlocks', 'resolve deadlocks', 'prevent deadlocks') but these are fairly limited variations. Missing natural terms users might say like 'thread stuck', 'application frozen', 'circular wait', 'lock contention'. | 2 / 3 |
Distinctiveness Conflict Risk | The deadlock-specific terminology provides some distinctiveness, but the vague capability description ('guidance and automation') could overlap with general debugging or concurrency skills. The trigger terms are specific enough to reduce major conflicts. | 2 / 3 |
Total | 7 / 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.