CC Error Resolver
Legacy error-resolution reference archive retained for migration. Do not route user tasks here; use systematic-debugging for active bug, stack-trace, and root-cause work.
Legacy error-resolution reference archive retained for migration.
As a process C 52/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, consistency
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The skill contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.
Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.
How to improve
- 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 · 5
✓ No critical or high findings
Medium and low: 5
-
medium Dangerous commands
cmd-privilegepatterns/docker.md:398Privilege escalation / world-writable permissionschmod 777 /host/path # Not recommended for production
-
medium Dangerous commands
cmd-privilegepatterns/nodejs.md:212Privilege escalation / world-writable permissionssudo chown $USER:$USER /path/to/file
-
medium Dangerous commands
cmd-privilegepatterns/nodejs.md:215Privilege escalation / world-writable permissionssudo chown -R $USER /usr/local/lib/node_modules
-
medium Dangerous commands
cmd-privilegepatterns/python.md:394Privilege escalation / world-writable permissionssudo chown $USER:$USER /path/to/file
-
low Dangerous commands
cmd-privilegereplay/README.md:297Privilege escalation / world-writable permissions (quoted — discussed, not commanded)- "chmod 777 /host/path" # Quick but not secure
quoted
Files scanned: 14. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - note
edit-residuethe text marks something as outdated (lines 4): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 52/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 2 mutating operations with no state check
- 40Consistency. Frontmatter name (Error Resolver) differs from the folder (error-resolver)
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (python) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 100Steps. 45 steps
- 100Execution cost. Instruction body is 2025 tokens
- low 10 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)
- +1No license
- +2Single-language instructions
- +3Description length 170: enough signal without eating the budget
- +4Structure: 29 headings
- +3Step-by-step instructions: 45 items
- +3Output format is stated explicitly
- +4Has examples (11 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 82.