BC senddy
Create and manage private stablecoin wallets using Senddy's zero-knowledge protocol on Base. Use when building payment agents, bots, server-side apps, or any system that needs private USDC transfers. Covers @senddy/node for headless agents and @senddy/client for browser apps.
As a process C 51/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- 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
-
low Secrets in code
secret-high-entropy-tokenreference.md:215High-entropy token-like string (may be an id, hash or a credential) (documentation table row)| Pool (V3) | `0x0b…648` |
table -
low Secrets in code
secret-high-entropy-tokenreference.md:216High-entropy token-like string (may be an id, hash or a credential) (documentation table row)| Attestor | `0xFa…e22` |
table -
low Secrets in code
secret-high-entropy-tokenreference.md:217High-entropy token-like string (may be an id, hash or a credential) (documentation table row)| USDC | `0x83…913` |
table -
low Secrets in code
secret-high-entropy-tokenreference.md:218High-entropy token-like string (may be an id, hash or a credential) (documentation table row)| Permit2 | `0x00…BA3` |
table -
low Secrets in code
secret-high-entropy-tokenSKILL.md:212High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)SHARED_CONTRACTS.USDC // '0x83…913'
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:213High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)SHAR…it2 // '0x00…BA3'
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:214High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)V3_C…ool // '0x0b…648'
quoted
Files scanned: 5. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 51/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 10 mutating operations with no state check
- 100Tools and files. No external tools needed
- 100Steps. 11 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2649 tokens
- 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
- -2localhost URLs: will not work for another user
- +1No license
- +2Single-language instructions
- +3Description length 276: enough signal without eating the budget
- +4Structure: 23 headings
- +3Step-by-step instructions: 11 items
- +4Has examples (20 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 82.