AB crypto-trading-decision-framework
Structured decision system for crypto traders — position sizing, entry checklist, exit framework, and halt decision tree. Eliminates ad-hoc calls and enforces disciplined risk management on every trade. Use when sizing a new position, evaluating an entry, managing a live trade, or deciding when to halt a strategy. Prevents the most common trader failure modes: oversizing, moving stops, and holding losers.
As a process B 68/100 · Nearly there — weak spots: when it triggers, inputs and preconditions, progress reporting
How to improve
- 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 409 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period) - note
frontmatter-keyunknown frontmatter key "emoji"
Process rating: all ten parameters 68/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 60Result and completion. Output format stated, no completion criterion
- 60Failures and branches. 2 branches
- 100Tools and files. No external tools needed
- 100Steps. 52 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1577 tokens
- 100Running it twice. Mutating operations check current state
- low 10 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)
- -215 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +3Description length 408: enough signal without eating the budget
- +4Structure: 16 headings
- +3Step-by-step instructions: 52 items
- +3Output format is stated explicitly
- +4Has examples (3 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 78.