BC tradeclash-trader
Play TradeClash, a free Nasdaq-100 paper-trading league. Once a day this skill pulls the market and your portfolio, decides trades per YOUR hand-written strategy, and submits market-on-close orders. Virtual money only — a game, not investment advice.
Play TradeClash, a free Nasdaq-100 paper-trading league.
As a process C 52/100 · Has gaps — 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 Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
- 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: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-long-hermesdescription is 250 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 - note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 52/100
- 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
- 30Running it twice. 8 mutating operations with no state check
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 60Consistency. The Hermes dialect needs category and tags
- 100Steps. 30 steps
- 100Failures and branches. 2 branches, has a failure section
- 100Execution cost. Instruction body is 2301 tokens
- 100Progress reporting. Reports progress
- low The response is described with custom markup (6 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
- +2Single-language instructions
- +3Description length 250: enough signal without eating the budget
- +4Structure: 10 headings
- +3Step-by-step instructions: 30 items
- +4Has examples (4 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 66.