AF polymarket-daily-anomalies
Polymarket Daily Anomaly Report. Scans for 3 types of market anomalies: Black Swan (sudden probability shifts in 2h windows), Whale Wars (large opposing bets on same market), Insider Watch (suspicious new-wallet large buys on low-probability outcomes). Generates a narrative daily report with real news context. Trigger words: daily report, anomaly report, market anomalies, insider watch, whale wars, black swan, daily brief, market monitor, what happened today, any anomalies, unusual activity. Auto-trigger when user asks 'generate today's report', 'any insider activity', 'any whale wars today', 'black swan events', 'market anomalies'.
As a process F 52/100 · Will not run — References files that are not bundled: URL
How to improve
- 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: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: URL
Process rating: all ten parameters 52/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
- 30Running it twice. 3 mutating operations with no state check
- 40Consistency. Frontmatter name (polymarket-daily-anomalies) differs from the folder (polymarket-predictradar-daily-anomalies-skills)
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 100Steps. 40 steps
- 100Failures and branches. 4 branches, has a failure section
- 100Execution cost. Instruction body is 3995 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 11 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)
- +1No license
- +2Single-language instructions
- +3Description length 640: enough signal without eating the budget
- +4Structure: 33 headings
- +3Step-by-step instructions: 40 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: 84.