AC poly-master
Polymarket prediction market skill by Antalpha AI. Discover trending markets, browse event predictions, invest in outcomes, copy-trade top traders, track portfolio & PnL. V3: Antalpha wallet data, trader win-rate enrichment, event money-flow heat, and Poly Master hedge strategy. Trigger: polymarket, prediction market, 预测市场, poly, copy trade, 跟单, wallet profile, 钱包画像, smart money, hedge strategy, 对冲策略, arbitrage, 套利
As a process C 51/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- 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 · 2
✓ No critical or high findings
Medium and low: 2
-
low Secrets in code
secret-high-entropy-tokenSKILL.md:48High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)- **Currency**: USDC.e (`0x27…174`)
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:386High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)- **USDC.e (Polygon)**: `0x27…174`
quoted
Files scanned: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
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
- 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
- 30Running it twice. 1 mutating operations with no state check
- 100Tools and files. No external tools needed
- 100Steps. 32 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2898 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 14 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)
- +3Output format is not stated: the model decides each time
- -220 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +3Description length 418: enough signal without eating the budget
- +4Structure: 37 headings
- +3Step-by-step instructions: 32 items
- +4Has examples (13 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 86.