BC command-execution
Execute terminal commands safely with preflight checks and risk gating.
As a process C 61/100 · Has gaps — weak spots: when it triggers, consistency, running it twice
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 · 2
✓ No critical or high findings
Medium and low: 2
-
medium Dangerous commands
cmd-pipe-to-shellcommand-execution.md:25Downloads and executes remote code from an unrecognised host (pipe to shell) (quoted — discussed, not commanded)- piping remote scripts (`curl ... | sh`)
quoted -
medium Dangerous commands
cmd-pipe-to-shellSKILL.md:35Downloads and executes remote code from an unrecognised host (pipe to shell) (quoted — discussed, not commanded)- piping remote scripts (`curl ... | sh`)
quoted
Files scanned: 5. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 61/100
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 3 mutating operations with no state check
- 40Consistency. Frontmatter name (command-execution) differs from the folder (axodus-command-execution)
- 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 60Failures and branches. 2 branches
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 34 steps
- 100Execution cost. Instruction body is 492 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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)
- +3Description length 71: 120–800 characters recommended
- +1No license
- +2Single-language instructions
- +4Structure: 9 headings
- +3Step-by-step instructions: 34 items
- +3Output format is stated explicitly
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.