BB typhoon-starknet-account
Create an anonymous Starknet wallet via Typhoon and interact with Starknet contracts. Privacy-focused wallet creation for agents requiring anonymity.
As a process B 70/100 · Nearly there — weak spots: result and completion, when it triggers, 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 asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.
Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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
✓ No critical or high findings
Medium and low: 4
-
medium Broad scope
meta-broad-allowed-toolsSKILL.md:1Broad tool permissions pre-approved: Bashallowed-tools: Bash Read Write Glob Grep Task
-
low Dangerous commands
cmd-cron-mentionscripts/watch-events-smart.js:117Mentions editing / listing crontab (quoted — discussed, not commanded)currentCrontab = execSync('crontab -l 2>/dev/null || echo ""').toString();quoted -
low Dangerous commands
cmd-cron-mentionscripts/watch-events-smart.js:265Mentions editing / listing crontab (quoted — discussed, not commanded)const currentCrontab = execSync('crontab -l 2>/dev/null || echo ""').toString();quoted -
low Dangerous commands
cmd-cron-mentionscripts/watch-events-smart.js:289Mentions editing / listing crontab (quoted — discussed, not commanded)const currentCrontab = execSync('crontab -l 2>/dev/null || echo ""').toString();quoted
Files scanned: 19. 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") - note
frontmatter-keyunknown frontmatter key "keywords"
Process rating: all ten parameters 70/100
- 0Result and completion. Does not say what the result is
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 2 mutating operations with no state check
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Tools and files. Tools declared in frontmatter
- 100Steps. 37 steps
- 100Failures and branches. 2 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1384 tokens
- 100Progress reporting. Reports progress
- low 11 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
- -41 reference files, but SKILL.md never points to them: the model will not open them
- -37 of 13 scripts are never mentioned in SKILL.md
- +2Single-language instructions
- +3Description length 149: enough signal without eating the budget
- +4Structure: 13 headings
- +3Step-by-step instructions: 37 items
- +4Has examples (10 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 65.