BC debug-detective
Activate this skill whenever a user needs help debugging, diagnosing, or profiling issues in their application. Covers systematic debugging methodology, git bisect, Chrome DevTools deep dive, Node.js and Python debugger usage, system-level debugging with strace and tcpdump, database query debugging with EXPLAIN ANALYZE, network debugging with curl and DNS tools, memory leak detection, CPU and performance profiling with flame graphs, structured logging and distributed tracing with OpenTelemetry, and production debugging strategies. Provides step-by-step workflows and a comprehensive pitfalls reference.
As a process C 50/100 · Has gaps — weak spots: result and completion, inputs and preconditions, failures and branches
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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 · 1
✓ No critical or high findings
Medium and low: 1
-
low Exfiltration
read-dotenvscripts/scaffold.sh:317Reads a .env file (code comment)# Usage: source .env.debug && node app.js
comment
Files scanned: 7. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 7706 tokens (recommended < 5000); move details to references/
Process rating: all ten parameters 50/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 30Running it twice. 2 mutating operations with no state check
- 60Tools and files. Uses tools (web, python, node) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 70Execution cost. Instruction body is 7706 tokens
- 100Steps. 25 steps
- 100Consistency. Name and required fields are in place
- 100Progress reporting. Reports progress
- low 14 top-level sections: this looks like several domains in one skill
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
- -2localhost URLs: will not work for another user
- -42 reference files, but SKILL.md never points to them: the model will not open them
- -31 of 1 scripts are never mentioned in SKILL.md
- +2Single-language instructions
- +3Description length 608: enough signal without eating the budget
- +4Structure: 67 headings
- +3Step-by-step instructions: 25 items
- +4Has examples (52 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 66.