AD ticktape
Pre-flight checks for Polymarket trading via the TickTape API (ticktape.cc). Use BEFORE sending a Polymarket order (slippage/depth/fee verdict), BEFORE copy-trading a wallet (copyability verdict), or when choosing whom to copy (leaderboard, red list). Trigger words: Polymarket order, preflight, slippage check, safe size, copy trade, copy this wallet, whale leaderboard, who to copy, red list, is this wallet worth copying, will this order move the market.
Pre-flight checks for Polymarket trading via the TickTape API (ticktape.cc). Use BEFORE sending a Polymarket order (slippage/depth/fee verdict), BEFORE…
As a process D 49/100 · Unfinished process — weak spots: result and completion, inputs and preconditions, consistency
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 · 0
✓ No critical or high findings
Files scanned: 3. 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 49/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 9 mutating operations with no state check
- 40Consistency. Frontmatter name (ticktape) differs from the folder (polymarket-preflight)
- 50When it triggers. No condition that starts the skill
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (web, node) that frontmatter does not declare
- 100Steps. 12 steps
- 100Execution cost. Instruction body is 1249 tokens
- 100Progress reporting. Reports progress
- 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
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 457: enough signal without eating the budget
- +4Structure: 10 headings
- +3Step-by-step instructions: 12 items
- +3Output format is stated explicitly
- +4Has examples (4 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 91.