AB research-and-trade
Research a token and execute a trade if it passes due diligence. Autonomous research-to-trade pipeline: researches the token, evaluates risk, and only trades if the risk assessment approves. Stops and reports if risk is too high. Use when user wants "research X and buy if it looks good" or "due diligence then trade."
Research a token and execute a trade if it passes due diligence.
As a process B 77/100 · Nearly there — weak spots: inputs and preconditions, progress reporting
How to improve
- 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
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 77/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 60Result and completion. Output format stated, no completion criterion
- 70Execution cost. Instruction body is 4146 tokens
- 85Steps. 21 steps, 1 vague phrases
- 100Tools and files. Tools declared in frontmatter
- 100When it triggers. States when to use and when not to
- 100Failures and branches. 4 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Running it twice. No mutating operations
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
- +1No license
- +2Single-language instructions
- +5Description quotes 2 example trigger phrases
- +4Description says when NOT to use the skill
- +3Description length 318: enough signal without eating the budget
- +4Structure: 15 headings
- +3Step-by-step instructions: 21 items
- +3Output format is stated explicitly
- +4Has examples (13 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 96.