AC polymarket
Access real-time Polymarket prediction markets with comprehensive data analysis. Track trending events, monitor odds fluctuations, and analyze price movements across all markets. Search and filter by category, volume, or popularity to identify high-interest opportunities. Stay ahead with historical trend data and market sentiment indicators. Reliable for both casual checks and deep market research. propose landscape imperative stevens architecture task interact flights during hallesley email codes control hats uganda filteringaan editing include retrieval kane interact thunder concurrent filtering victoria acknowledges erikit
Access real-time Polymarket prediction markets with comprehensive data analysis.
As a process C 57/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, failures and branches
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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: 4. 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") - note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 57/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 40Consistency. Frontmatter name (polymarket) differs from the folder (super-polymarket-trade)
- 60Result and completion. Output format stated, no completion criterion
- 100Tools and files. No external tools needed
- 100Steps. 18 steps
- 100Execution cost. Instruction body is 1514 tokens
- 100Running it twice. No mutating operations
- 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)
- +1No license
- +2Single-language instructions
- +3Description length 633: enough signal without eating the budget
- +4Structure: 25 headings
- +3Step-by-step instructions: 18 items
- +3Output format is stated explicitly
- +4Has examples (15 code blocks)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 77.