BC storage-private
Encrypted multi-node agent storage with automatic FilStream network discovery. Client-side ChaCha20-Poly1305 encryption, per-object DEKs, HKDF key derivation from ETH wallet. Replicates across memory stores, FilStream CDN, and local disk. On-chain payment via StorageCredits contract (Base mainnet, USDC). Zero npm dependencies.
As a process C 51/100 · Has gaps — weak spots: result and completion, when it triggers, failures and branches
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 · 2
✓ No critical or high findings
Medium and low: 2
-
low Secrets in code
secret-high-entropy-tokenSKILL.md:75High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)StorageCredits contract: `0x15…49F`
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:80High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)- **USDC:** `0x83…913` (Base)
quoted
Files scanned: 5. 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")
Process rating: all ten parameters 51/100
- 0Result and completion. Does not say what the result is
- 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. 1 mutating operations with no state check
- 60Tools and files. Uses tools (bash, web, node) that frontmatter does not declare
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 19 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 885 tokens
- 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 328: enough signal without eating the budget
- +4Structure: 10 headings
- +3Step-by-step instructions: 19 items
- +4Has examples (2 code blocks)
- +3All 2 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.