BF polymarket-market-discovery
Polymarket hot market rankings & new market discovery. View trending markets by 24h volume/traders, discover newly listed high-momentum markets, browse active markets by category. Triggers: trending markets, hot markets, top markets, what's hot, new markets, newly listed, just launched, high potential, fastest growing, which markets, market pulse, crypto markets, politics markets, sports markets, what can I trade, what markets are there. Auto-triggers on 'what are the hottest markets right now', 'any new markets', 'what crypto markets can I trade'.
As a process F 53/100 · Will not run — References files that are not bundled: url
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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: 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") - warning
body-longSKILL.md body ≈ 7360 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: url
Process rating: all ten parameters 53/100
- 0Tools and files. 1 referenced file(s) missing: url
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 40Consistency. Frontmatter name (polymarket-market-discovery) differs from the folder (polymarket-predictradar-market-discovery-skills)
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 70Execution cost. Instruction body is 7360 tokens
- 100Steps. 70 steps
- 100Failures and branches. 10 branches, has a failure section
- 100Running it twice. Mutating operations check current state
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 12 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)
- -213 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +3Description length 554: enough signal without eating the budget
- +4Structure: 34 headings
- +3Step-by-step instructions: 70 items
- +3Output format is stated explicitly
- +4Has examples (14 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 57.