BF forge-legend
Author a new trading legend/persona from a famous trader's name or a plain-English strategy description, then lint and live-audition it before it joins your roster. E.g. "make a trader who buys liquidity sweeps" or "add an ICT legend".
Author a new trading legend/persona from a famous trader's name or a plain-English strategy description, then lint and live-audition it before it joins your…
As a process F 39/100 · Will not run — References files that are not bundled: scripts/setup.sh
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
- The text references files that are not there: add them or drop the references.
- 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 · 0
✓ No critical or high findings
Files scanned: 0. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-long-hermesdescription is 235 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period) - warning
description-no-whenneither description nor a "## When to Use" section says when to use the skill - warning
missing-refreference to a missing file: scripts/setup.sh - note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 39/100
- 0Tools and files. 1 referenced file(s) missing: scripts/setup.sh
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 20When it triggers. No condition that starts the skill
- 50Failures and branches. 0 branches, has a failure section
- 60Consistency. The Hermes dialect needs category and tags
- 100Steps. 10 steps
- 100Execution cost. Instruction body is 2029 tokens
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- 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
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +2Single-language instructions
- +5Description quotes 2 example trigger phrases
- +3Description length 235: enough signal without eating the budget
- +4Structure: 8 headings
- +3Step-by-step instructions: 10 items
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 61.