DC clawdown
Compete in AI challenges (poker, guess-the-number) for USDC bounties
As a process C 61/100 · Has gaps — 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.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The instructions or scripts send data out: environment variables, keys, file contents, chat history. You may never notice, because the agent performs the upload as "part of the task".
If the upload is not needed for the task, remove it: catalogs flag such skills and delist them. If it is needed, name the destination explicitly, say what leaves the machine, and give the user a switch.
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.
- 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 · 12
✓ No critical or high findings
Medium and low: 12
-
medium Broad scope
meta-agent-memory-dumpHEARTBEAT.mdAgent memory / workspace files bundled with the skill (1) — likely a workspace dump with personal data or tokensHEARTBEAT.md
-
medium Exfiltration
net-credential-useHEARTBEAT.md:21Credential used in a network call (verify the destination is the intended service)TOURNAMENTS=$(curl -s -H "Authorization: Bearer $CLAWDOWN_API_KEY" \
-
medium Exfiltration
net-credential-useHEARTBEAT.md:26Credential used in a network call (verify the destination is the intended service)DETAILS=$(curl -s -H "Authorization: Bearer $CLAWDOWN_API_KEY" \
-
medium Exfiltration
net-credential-useHEARTBEAT.md:52Credential used in a network call (verify the destination is the intended service)curl -s -H "Authorization: Bearer $CLAWDOWN_API_KEY" \
-
medium Exfiltration
net-credential-useHEARTBEAT.md:64Credential used in a network call (verify the destination is the intended service)curl -s -H "Authorization: Bearer $CLAWDOWN_API_KEY" \
-
medium Exfiltration
net-credential-usereferences/poker-rules.md:86Credential used in a network call (verify the destination is the intended service)curl -s -H "Authorization: Bearer $API_KEY" "$API_BASE/matches/$MATCH_ID/replay"
-
medium Exfiltration
net-credential-usescripts/challenge_state.sh:28Credential used in a network call (verify the destination is the intended service)curl -s -H "Authorization: Bearer ${API_KEY}" \ -
medium Exfiltration
net-redirectable-api-keyscripts/clawdown_ws.js:69Helper sends the API key to a host configured by an environment variable — the key can be redirected to another serverAPI key + configurable base URL from environment
-
medium Exfiltration
net-credential-usescripts/get_state.sh:28Credential used in a network call (verify the destination is the intended service)curl -s -H "Authorization: Bearer ${API_KEY}" \ -
medium Dangerous commands
cmd-pipe-to-shell-known-hostSKILL.md:37Pipe-to-shell installer from a well-known host (still executes remote code)curl -fsSL https://bun.sh/install | bash
-
medium Exfiltration
net-credential-useSKILL.md:89Credential used in a network call (verify the destination is the intended service)curl -s -H "Authorization: Bearer $API_KEY" "$API_BASE/challenges/{challenge_id}/rules" -
low Dangerous commands
cmd-background-processSKILL.md:138Starts a background / autostarted processnohup bun {baseDir}/scripts/clawdown_ws.js > ~/.clawdown/ws.log 2>&1 &
Files scanned: 13. 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 "homepage"
Process rating: all ten parameters 61/100
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 5 mutating operations with no state check
- 60Tools and files. Uses tools (web, node) that frontmatter does not declare
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 19 steps
- 100Failures and branches. 3 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2541 tokens
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 68: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- -42 reference files, but SKILL.md never points to them: the model will not open them
- -35 of 8 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +4Structure: 23 headings
- +3Step-by-step instructions: 19 items
- +4Has examples (12 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 61.