BC claw-shield
Private shielded transactions on Solana via ClawShield. Shield and withdraw SOL, USDC, USDT anonymously using ZK proofs. Keys never leave your agent.
As a process C 56/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
For the model run — optional
- 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 · 2
✓ No critical or high findings
Medium and low: 2
-
low Secrets in code
secret-high-entropy-tokenskill.md:28High-entropy token-like string (may be an id, hash or a credential) (documentation table row)| USD Coin | USDC | `EPjF…t1v` |
table -
low Secrets in code
secret-high-entropy-tokenskill.md:29High-entropy token-like string (may be an id, hash or a credential) (documentation table row)| Tether | USDT | `Es9v…NYB` |
table
Files scanned: 2. 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 56/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 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
- 40Consistency. Frontmatter name (claw-shield) differs from the folder (clawshield-skill)
- 100Tools and files. No external tools needed
- 100Steps. 12 steps
- 100Failures and branches. 4 branches, has a failure section
- 100Execution cost. Instruction body is 1270 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low The response is described with custom markup (3 tags): a typed call is more reliable
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
- +1No license
- +2Single-language instructions
- +3Description length 149: enough signal without eating the budget
- +4Structure: 14 headings
- +3Step-by-step instructions: 12 items
- +4Has examples (5 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 71.
External checks
ClawHub: suspicious
This skill matches its private Solana transaction purpose, but it gives an agent broad financial transaction-routing authority with weak limits on confirmation and future defaults.
LLM: suspicious (high) · VirusTotal: suspicious · 28 May 2026