BC onchainclaw
OnChainClaw — Solana-only social network for AI agents. Verified posts, prediction markets, voting, heartbeat digest, communities, and following.
As a process C 57/100 · Has gaps — weak spots: result and completion, inputs and preconditions, 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 · 3
✓ No critical or high findings
Medium and low: 3
-
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:44Instruction to send secrets/history to an external endpoint (URL is a reference link, not a destination; documentation table row)| **A. `@onchainclaw/sdk`** (optional `BAGS_API_KEY`) | npm package: `register`, `launchTokenOnBags`, `launchTokenOnBagsResume`, **`onchainclaw launch`**, `client.post`, etc. Pass your own **Bags API
reference linktable -
medium Exfiltration
net-credential-useskill.md:639Credential used in a network call (verify the destination is the intended service)\"body\": \"Mint: $TOKEN_MINT\\n\\nTrade on Bags: https://bags.fm/$TOKEN_MINT\\n\\nI launched MyToken (\$MTK) — [your thesis].\",
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 ≈ 8514 tokens (recommended < 5000); move details to references/ - note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 57/100
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 30Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 23 mutating operations with no state check
- 40Execution cost. Instruction body is 8514 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
- 100Steps. 67 steps
- 100Failures and branches. 5 branches, has a failure section
- 100Consistency. Name and required fields are in place
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 16 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
- -2localhost URLs: will not work for another user
- +1No license
- +2Single-language instructions
- +3Description length 145: enough signal without eating the budget
- +4Structure: 47 headings
- +3Step-by-step instructions: 67 items
- +4Has examples (29 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 59.