BC solidity-audit
Solidity smart contract security audit assistant following EEA EthTrust V3 specification. Performs structured audit workflow: vulnerability scanning, security analysis, audit reports. Detects reentrancy, integer overflow, access control issues, and more. Supports Slither/Aderyn static analysis and Foundry testing. Triggers: smart contract audit, solidity audit, security review, vulnerability assessment.
As a process C 63/100 · Has gaps — weak spots: result and completion, failures and branches, progress reporting
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
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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 · 3
✓ No critical or high findings
Medium and low: 3
-
medium Dangerous commands
cmd-pipe-to-shellreferences/toolchain-guide.md:51Downloads and executes remote code from an unrecognised host (pipe to shell) (documentation of a security skill)curl -L https://foundry.paradigm.xyz | bash
security skill -
medium Dangerous commands
cmd-pipe-to-shellSKILL.md:523Downloads and executes remote code from an unrecognised host (pipe to shell) (documentation of a security skill)curl -L https://foundry.paradigm.xyz | bash
security skill -
low Dangerous commands
cmd-pipe-to-shellreferences/testing-guide.md:11Downloads and executes remote code from an unrecognised host (pipe to shell) (test fixture / example file; documentation of a security skill)curl -L https://foundry.paradigm.xyz | bash
fixturesecurity skill
Files scanned: 12. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
body-longSKILL.md body ≈ 6805 tokens (recommended < 5000); move details to references/
Process rating: all ten parameters 63/100
- 0Result and completion. Does not say what the result is
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 50When it triggers. No condition that starts the skill
- 70Inputs and preconditions. Inputs and preconditions are listed
- 70Execution cost. Instruction body is 6805 tokens
- 100Tools and files. No external tools needed
- 100Steps. 72 steps
- 100Consistency. Name and required fields are in place
- 100Running it twice. Mutating operations check current state
- 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)
- +3Output format is not stated: the model decides each time
- -31 of 1 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 406: enough signal without eating the budget
- +4Structure: 71 headings
- +3Step-by-step instructions: 72 items
- +4Has examples (32 code blocks)
- +4Reference files are cited in the instructions (5 of 7)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 63.