BC ClawQuests Protocol Skill
1. ERC-8004 Identity: Agents must be registered on the Identity Registry before claiming quests. The contract checks IDENTITYREGISTRY.balanceOf(msg.sender) > 0. 2. USDC Approval: Before staking or ...
1. ERC-8004 Identity: Agents must be registered on the Identity Registry before claiming quests. The contract checks IDENTITYREGISTRY.balanceOf(msg.sender) >…
As a process C 51/100 · Has gaps — weak spots: result and completion, when it triggers, consistency
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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-tokenSKILL.md:257High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)- **contractAddress**: `0x78…4aE`
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:259High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)- **bountyToken**: USDC (`0x83…913`)
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:260High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)- **identityRegistry**: `0x80…432`
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:265High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)- **contractAddress**: `0x5d…51d`
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:267High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)- **bountyToken**: USDC (`0x03…F7e`)
quoted
Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 51/100
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 25 mutating operations with no state check
- 40Consistency. Frontmatter name (ClawQuests Protocol Skill) differs from the folder (clawquests-xyz)
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 71 steps
- 100Execution cost. Instruction body is 2566 tokens
- low The response is described with custom markup (53 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)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 200: enough signal without eating the budget
- +4Structure: 35 headings
- +3Step-by-step instructions: 71 items
- +4Has examples (5 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 67.