CC pinata-erc-8004
Register and verify ERC-8004 AI agents on-chain using Pinata IPFS and Viem for blockchain transactions
Register and verify ERC-8004 AI agents on-chain using Pinata IPFS and Viem for blockchain transactions
As a process C 63/100 · Has gaps — weak spots: inputs and preconditions, running it twice
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 purpose itself is risky: wallets, browser password stores, offensive security. Even an honest implementation gives the agent access to things that cost money.
Explain in the description why the access is needed and how it is limited; add tests that show refusals on dangerous requests.
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 · 6
✓ No critical or high findings
Medium and low: 6
-
medium Risky intent
intent-wallet-secretsSKILL.md:21Handles crypto-wallet secrets (seed / mnemonic / private key) — a classic stealer target1. **PRIVATE_KEY (Ethereum wallet private key)**
-
medium Risky intent
intent-wallet-secretsSKILL.md:352Handles crypto-wallet secrets (seed / mnemonic / private key) — a classic stealer target- `PRIVATE_KEY` - Ethereum wallet private key (with 0x prefix) for signing transactions - **USE A DEDICATED WALLET WITH MINIMAL FUNDS**
-
medium Risky intent
intent-wallet-secretsSKILL.md:817Handles crypto-wallet secrets (seed / mnemonic / private key) — a classic stealer target- Use hex string, not mnemonic phrase
-
low Secrets in code
secret-high-entropy-tokenSKILL.md:456High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)- Contract Address: MUST be one of the two official registry addresses listed in "OFFICIAL ERC-8004 IDENTITY REGISTRY ADDRESSES" section. Mainnet: `0x80…432`. Testnet
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:754High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)- **Address:** `0x80…432`
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:758High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)- **Address:** `0x80…D9e`
quoted
Files scanned: 1. 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 ≈ 7549 tokens (recommended < 5000); move details to references/ - note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 63/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 13 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 60Tools and files. Uses tools (bash, write, web) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70Execution cost. Instruction body is 7549 tokens
- 85Steps. 312 steps, 2 vague phrases
- 100Failures and branches. 2 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 22 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)
- +3Description length 102: 120–800 characters recommended
- -216 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +4Structure: 75 headings
- +3Step-by-step instructions: 312 items
- +3Output format is stated explicitly
- +4Has examples (11 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 59.