BD jb-interact-ui
Generate minimal frontends for interacting with existing Juicebox V5 projects. Pay, cash out, claim tokens, view project state - all in standalone HTML files.
Generate minimal frontends for interacting with existing Juicebox V5 projects.
As a process D 40/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
GeneratorSoftware developmentData and analyticstype 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 SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
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 · 4
✓ No critical or high findings
Medium and low: 4
-
low Secrets in code
secret-high-entropy-tokenSKILL.md:89High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)const NATIVE_TOKEN = '0x00…EEe';
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:258High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)const NATIVE_TOKEN = '0x00…EEe';
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:382High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)const NATIVE_TOKEN = '0x00…EEe';
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:574High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)const NATIVE_TOKEN = '0x00…EEe';
quoted
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
body-longSKILL.md body ≈ 12650 tokens (recommended < 5000); move details to references/
Process rating: all ten parameters 40/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. 2 mutating operations with no state check
- 40Execution cost. Instruction body is 12650 tokens: crowds the task out of the window
- 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
- 100Steps. 14 steps
- 100Consistency. Name and required fields are in place
- low 11 top-level sections: this looks like several domains in one skill
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 158: enough signal without eating the budget
- +4Structure: 12 headings
- +3Step-by-step instructions: 14 items
- +4Has examples (8 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 62.