BC indigo-ipfs
Store and retrieve data on IPFS and query collector UTXOs for the Indigo Protocol.
As a process C 53/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 · 5
✓ No critical or high findings
Medium and low: 5
-
low Secrets in code
secret-high-entropy-tokensub-skills/ipfs-storage.md:50High-entropy token-like string (may be an id, hash or a credential)CID: QmX7…yBn
-
low Secrets in code
secret-high-entropy-tokensub-skills/ipfs-storage.md:61High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)**Prompt:** "Retrieve the content at CID QmX7…yBn"
quoted -
low Secrets in code
secret-high-entropy-tokensub-skills/ipfs-storage.md:68High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"cid": "QmX7…yBn"
quoted -
low Secrets in code
secret-high-entropy-tokensub-skills/ipfs-storage.md:78High-entropy token-like string (may be an id, hash or a credential)CID: QmX7…yBn
-
low Secrets in code
secret-high-entropy-tokensub-skills/ipfs-storage.md:114High-entropy token-like string (may be an id, hash or a credential)CID: QmR4…pXn
Files scanned: 6. 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 53/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
- 100Tools and files. Tools declared in frontmatter
- 100Steps. 4 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 345 tokens
- 100Running it twice. No mutating operations
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 82: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +2Single-language instructions
- +4Structure: 7 headings
- +3Step-by-step instructions: 4 items
- +4Reference files are cited in the instructions (2 of 2)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 70.
External checks
ClawHub: suspicious
The skill is coherent and instruction-only, but it encourages storing plain-text and wallet-linked financial snapshots on IPFS without clear public and hard-to-delete data warnings.
LLM: suspicious (high) · VirusTotal: · 29 May 2026