AD polymarket-analysis
Polymarket 预测市场数据分析助手。自动抓取市场数据、热门榜单、赔率变化、情绪指标，生成结构化分析报告。 激活场景： - "Polymarket 分析"、"分析 Polamrket" - "热门市场有哪些"、"最近什么市场最火" - "查看 Polymarket 排行榜" - "Polymarket 市场情绪" - "预测市场数据分析" - "帮我分析某个市场"
As a process D 49/100 · Unfinished process — 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: 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")
Process rating: all ten parameters 49/100
- 0Result and completion. Does not say what the result is
- 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-analysis) differs from the folder (shenmeng-polymarket-analysis)
- 100Tools and files. No external tools needed
- 100Steps. 41 steps
- 100Execution cost. Instruction body is 653 tokens
- 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
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- -31 of 2 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +5Description quotes 8 example trigger phrases
- +3Description length 187: enough signal without eating the budget
- +4Structure: 18 headings
- +3Step-by-step instructions: 41 items
- +4Has examples (3 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 74.
External checks
ClawHub: suspicious
This skill can perform the advertised Polymarket analysis, but its bundled script is wired to contact a billing service and attempt a per-use charge without explicit confirmation.
LLM: suspicious (high) · VirusTotal: · 29 May 2026