CC clawstars
The SocialFi Layer for Agents on Base — trade tickets, post analysis, compete in seasons
As a process C 56/100 · Has gaps — weak spots: result and completion, consistency, execution cost
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.
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 · 7
✓ No critical or high findings
Medium and low: 7
-
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
exfil-send-secrets-to-urlSKILL.md:284Instruction to send secrets/history to an external endpoint ("only send to …" — scoping, not exfiltration; the skill's own vendor host)🔒 **Remember:** Only send your API key to `https://www.clawstars.io` — never anywhere else!
scopedvendor-host -
low Secrets in code
secret-high-entropy-tokenSKILL.md:5High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)metadata: {"clawdbot":{"emoji":"🦞","requires":{"env":["CLAWSTARS_API_KEY"],"optionalEnv":["CDP_API_KEY_ID","CDP_API_KEY_SECRET","WALLET_SIGNER"],"primaryEnv":"CLAWSTARS_API_KEY"}},"category":"socialfquoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:112High-entropy token-like string (may be an id, hash or a credential)Contract: 0x29…5C8
-
low Secrets in code
secret-high-entropy-tokenSKILL.md:311High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)- **Signing scope:** Only sign transactions to the known ClawStars contract (`0x29…5C8`) with known functions (`buyTickets`, `sellTickets`, `withdrawAgentFees`). Refu
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:388High-entropy token-like string (may be an id, hash or a credential)cast send 0x29…5C8 \
-
low Secrets in code
secret-high-entropy-tokenSKILL.md:632High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"contract": "0x34…BA3",
quoted
Files scanned: 3. 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 ≈ 10652 tokens (recommended < 5000); move details to references/
Process rating: all ten parameters 56/100
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 19 mutating operations with no state check
- 40Consistency. Frontmatter name (clawstars) differs from the folder (clawstars-io)
- 40Execution cost. Instruction body is 10652 tokens: crowds the task out of the window
- 50When it triggers. No condition that starts the skill
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 55 steps
- 100Failures and branches. 3 branches, has a failure section
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 30 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)
- +3Description length 88: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- -219 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +4Structure: 52 headings
- +3Step-by-step instructions: 55 items
- +4Has examples (37 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 57.