CC moss-trade-bot-factory-en
Users describe a trading style in natural language, and the skill creates a crypto trading bot, runs local backtests, supports periodic reflection-driven evolution, and can optionally connect to an external platform for verification and simulated live trading.
Users describe a trading style in natural language, and the skill creates a crypto trading bot, runs local backtests, supports periodic reflection-driven…
As a process C 52/100 · Has gaps — References files that are not bundled: scripts/data_BTC_USDT_15m_148d.csv
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.
- 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: 24. 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: scripts/data_BTC_USDT_15m_148d.csv - note
edit-residuethe text marks something as outdated (lines 91): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 52/100
- 0Tools and files. 1 referenced file(s) missing: scripts/data_BTC_USDT_15m_148d.csv
- 0Result and completion. Does not say what the result is
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 3 mutating operations with no state check
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 56 steps
- 100Failures and branches. 5 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2869 tokens
- 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
- +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
- -34 of 9 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 260: enough signal without eating the budget
- +4Structure: 12 headings
- +3Step-by-step instructions: 56 items
- +4Has examples (10 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 63.