DC erc8004-identity
(no description)
Not recommendedlow grade D
As a process C 56/100 · Has gaps — weak spots: result and completion, when it triggers, failures and branches
How to improve
- Add a description to the frontmatter: without it the skill never triggers.
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-tokencli.js:8High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)const IDENTITY_REGISTRY = "0x80…432";
quoted -
low Secrets in code
secret-high-entropy-tokencli.js:9High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)const REPUTATION_REGISTRY = "0x80…b63";
quoted -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:40High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…jgR+Mkmf+D189…ihQ==",
detector -
low Secrets in code
secret-high-entropy-tokenSKILL.md:118High-entropy token-like string (may be an id, hash or a credential) (documentation table row)| Identity Registry | `0x80…432` |
table -
low Secrets in code
secret-high-entropy-tokenSKILL.md:119High-entropy token-like string (may be an id, hash or a credential) (documentation table row)| Reputation Registry | `0x80…b63` |
table
Files scanned: 7. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- error
frontmatterSKILL.md: no YAML frontmatter block found - error
name-missingSKILL.md: frontmatter has no `name` - error
description-missingSKILL.md: no `description` — the skill can never trigger
Process rating: all ten parameters 56/100
- 0Result and completion. Does not say what the result is
- 0When it triggers. No condition that starts the skill
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 9 mutating operations with no state check
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Tools and files. No external tools needed
- 100Steps. 23 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 851 tokens
- low 11 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (4 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)
- +3Description length 0: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Structure: 19 headings
- +3Step-by-step instructions: 23 items
- +4Has examples (10 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 0.
External checks
ClawHub: suspicious
This skill has a coherent Avalanche identity purpose, but it handles wallet private keys and can trigger irreversible mainnet transactions without enough guardrails, including a deploy bug that can leave users with a paid partial setup.
LLM: suspicious (high) · VirusTotal: benign · 10 Sept 2026