CC anvil
Building CLI/TUI tools and configuring personal developer environments. Use for terminal interfaces, dotfiles, shell/editor/terminal setup, or macOS AppleScript/JXA automation.
Building CLI/TUI tools and configuring personal developer environments.
As a process C 61/100 · Has gaps — weak spots: inputs and preconditions
What is at stake
The skill contains fragments that, in the wrong hands, cost money or data. Below: what the installer risks and what the author should do.
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
- Address the high-severity findings: each costs 18 safety points. If one is a false positive, add the rule id to guard.allow in spec.yaml.
- 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 · 4
-
high Dangerous commands
cmd-pipe-to-shellreference/pkg-distribution.md:27Downloads and executes remote code from an unrecognised host (pipe to shell)| Static binary on releases | All | Universal fallback; curl \| sh install script | Users need auto-update |
Medium and low: 3
-
medium Dangerous commands
cmd-pipe-to-shellreference/pkg-distribution.md:117Downloads and executes remote code from an unrecognised host (pipe to shell) (quoted — discussed, not commanded)Publish checksums (`SHA256SUMS`) and their signature (`SHA2…sig` or `.intoto.jsonl` attestation) alongside every release. Users installing via `curl | sh` must be able to verify.
quoted -
medium Dangerous commands
cmd-pipe-to-shellreference/pkg-distribution.md:167Downloads and executes remote code from an unrecognised host (pipe to shell) (quoted — discussed, not commanded)- `curl | sudo bash` install scripts that do not verify checksums — one compromised CDN hop owns every user.
quoted -
low Dangerous commands
cmd-privilegereference/pkg-distribution.md:167Privilege escalation / world-writable permissions (quoted — discussed, not commanded)- `curl | sudo bash` install scripts that do not verify checksums — one compromised CDN hop owns every user.
quoted
Files scanned: 14. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 5822 tokens (recommended < 5000); move details to references/
Process rating: all ten parameters 61/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 50When it triggers. No condition that starts the skill
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70Execution cost. Instruction body is 5822 tokens
- 85Steps. 115 steps, 1 vague phrases
- 100Consistency. Name and required fields are in place
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- low 13 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)
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 176: enough signal without eating the budget
- +4Structure: 17 headings
- +3Step-by-step instructions: 115 items
- +3Output format is stated explicitly
- +4Reference files are cited in the instructions (11 of 11)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 77.