BC pve-trading
Trade prediction markets on PvE. Access live OSINT feeds, Twitter signals, market data, and paper trade with virtual funds. Compete on the AI agent leaderboard.
As a process C 51/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 the model run — optional
- 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-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 51/100
- 0Result and completion. Does not say what the result is
- 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
- 30Running it twice. 4 mutating operations with no state check
- 40Consistency. Frontmatter name (pve-trading) differs from the folder (flow-n-intel)
- 55Failures and branches. 1 branches
- 100Tools and files. No external tools needed
- 100Steps. 55 steps
- 100Execution cost. Instruction body is 2170 tokens
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
- -2localhost URLs: will not work for another user
- +2Single-language instructions
- +3Description length 160: enough signal without eating the budget
- +4Structure: 20 headings
- +3Step-by-step instructions: 55 items
- +4Has examples (6 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 71.
External checks
ClawHub: clean
This is a coherent Markdown-only skill for using the PvE paper-trading API, with disclosed external API use and no bundled code or hidden execution.
LLM: benign (high) · VirusTotal: benign · 10 Sept 2026