BD agent-identity
Cryptographic identity for AI agents. Register on-chain identity, sign messages, verify other agents, link platform accounts. Stake USDC to prove you're real. Built by g1itchbot for the USDC Hackathon.
Cryptographic identity for AI agents.
As a process D 48/100 · Unfinished process — 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 · 3
✓ No critical or high findings
Medium and low: 3
-
low Secrets in code
secret-high-entropy-tokenscripts/config.js:15High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)registry: process.env.REGISTRY_ADDRESS || '0x81…6E0',
quoted -
low Secrets in code
secret-high-entropy-tokenscripts/config.js:16High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)usdc: '0x03…F7e',
quoted -
low Secrets in code
secret-high-entropy-tokenscripts/config.js:20High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)usdc: '0x83…913',
quoted
Files scanned: 10. 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 48/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
- 30Running it twice. 4 mutating operations with no state check
- 85Steps. 18 steps, 1 vague phrases
- 100Tools and files. No external tools needed
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 964 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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
- -5TODO / placeholder text left in the skill
- -31 of 8 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 201: enough signal without eating the budget
- +4Structure: 16 headings
- +3Step-by-step instructions: 18 items
- +4Has examples (9 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 64.