AB get-agent-identity
Check your agent's on-chain ERC-8004 identity, trust score, and KYA credentials. Use when the user wants to see agent identity, check trust score, view credentials, or check agent status. Covers "agent ID", "trust score", "show my identity", "agent status", "KYA".
As a process B 69/100 · Nearly there — weak spots: result and completion, running it twice, progress reporting
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 · 4
✓ No critical or high findings
Medium and low: 4
-
low Secrets in code
secret-high-entropy-tokenSKILL.md:55High-entropy token-like string (may be an id, hash or a credential) (documentation table row)| Identity Registry | Base Mainnet | `0x80…432` |
table -
low Secrets in code
secret-high-entropy-tokenSKILL.md:56High-entropy token-like string (may be an id, hash or a credential) (documentation table row)| Identity Registry | Base Sepolia | `0x80…D9e` |
table -
low Secrets in code
secret-high-entropy-tokenSKILL.md:57High-entropy token-like string (may be an id, hash or a credential) (documentation table row)| Reputation | Base Mainnet | `0x80…b63` |
table -
low Secrets in code
secret-high-entropy-tokenSKILL.md:58High-entropy token-like string (may be an id, hash or a credential) (documentation table row)| Reputation | Base Sepolia | `0x80…713` |
table
Files scanned: 2. 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 69/100
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 2 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 70When it triggers. States when to use, but not when not to
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Tools and files. Tools declared in frontmatter
- 100Steps. 12 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 710 tokens
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
- +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
- +5Description quotes 4 example trigger phrases
- +3Description length 264: enough signal without eating the budget
- +4Structure: 8 headings
- +3Step-by-step instructions: 12 items
- +4Has examples (2 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 89.