BF alibabacloud-history-lock-diagnose
Alibaba Cloud PolarDB/RDS MySQL historical lock wait root cause analysis skill. Diagnoses and analyzes historical lock wait issues, identifies the complete lock chain and lock holder. Triggers: lock diagnosis, lock wait troubleshooting, deadlock analysis, PolarDB lock issue, RDS lock issue, lock wait timeout, transaction blocking, metadata lock wait, InnoDB lock analysis, database lock troubleshooting, MySQL lock wait, database performance troubleshooting, lock conflict analysis. Use when the user mentions database lock, deadlock, lock wait, transaction blocking, or slow queries related to locks.
Alibaba Cloud PolarDB/RDS MySQL historical lock wait root cause analysis skill.
As a process F 42/100 · Will not run — References files that are not bundled: references/ram-policies.md, references/related-commands.md, references/best-practices.md
How to improve
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 0. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: references/ram-policies.md - warning
missing-refreference to a missing file: references/related-commands.md - warning
missing-refreference to a missing file: references/best-practices.md - warning
missing-refreference to a missing file: references/acceptance-criteria.md - warning
missing-refreference to a missing file: references/cli-installation-guide.md - warning
missing-refreference to a missing file: references/transaction-lifecycle.md - warning
missing-refreference to a missing file: references/verification-method.md - warning
missing-refreference to a missing file: scripts/smart-lock-diagnosis.py
Process rating: all ten parameters 42/100
- 0Tools and files. 8 referenced file(s) missing: references/ram-policies.md, references/related-commands.md, references/best-practices.md
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 3 mutating operations with no state check
- 40Result and completion. Does not say what the result is
- 70When it triggers. States when to use, but not when not to
- 85Steps. 19 steps, 3 vague phrases
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1578 tokens
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 603: enough signal without eating the budget
- +4Structure: 13 headings
- +3Step-by-step instructions: 19 items
- +4Has examples (4 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.