BF jb-explorer-ui
Etherscan-like contract explorer for Juicebox projects. Read contract state, write transactions, and decode events.
Etherscan-like contract explorer for Juicebox projects.
As a process F 31/100 · Will not run — References files that are not bundled: ...args
GeneratorSoftware developmentAI and agentstype and topics are labelled automatically from the skill text
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The text references files that are not there: add them or drop the references.
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-tokenSKILL.md:422High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)1: { rpc: 'https://eth.llamarpc.com', contracts: { JBController: '0x0A…23e' }},quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:423High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)10: { rpc: 'https://optimism.llamarpc.com', contracts: { JBController: '0x0A…23e' }},quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:424High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)8453: { rpc: 'https://base.llamarpc.com', contracts: { JBController: '0x0A…23e' }},quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:425High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)42161: { rpc: 'https://arbitrum.llamarpc.com', contracts: { JBController: '0x0A…23e' }},quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:426High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)11155111: { rpc: 'https://sepolia.drpc.org', contracts: { JBController: '0x0A…23e' }}detector
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
missing-refreference to a missing file: ...args
Process rating: all ten parameters 31/100
Will not run. References files that are not bundled: ...args
- 0Tools and files. 1 referenced file(s) missing: ...args
- 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. 3 mutating operations with no state check
- 70Execution cost. Instruction body is 4872 tokens
- 100Steps. 12 steps
- 100Consistency. Name and required fields are in place
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 115: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Structure: 10 headings
- +3Step-by-step instructions: 12 items
- +4Has examples (3 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 63.