divergence
Spot vs Polymarket divergence trading on 15-minute crypto markets
64
56%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./src/skills/bundled/divergence/SKILL.mdQuality
Discovery
40%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description identifies a very specific niche (spot vs Polymarket divergence trading on 15-minute crypto markets), which gives it strong distinctiveness. However, it reads more like a topic label than a functional skill description—it lacks concrete actions the skill performs and entirely omits guidance on when Claude should select it. Adding explicit actions and a 'Use when...' clause would significantly improve its utility for skill selection.
Suggestions
Add a 'Use when...' clause specifying trigger scenarios, e.g., 'Use when the user asks about arbitrage opportunities between spot crypto prices and Polymarket prediction markets, or mentions divergence trading strategies.'
List specific concrete actions the skill performs, e.g., 'Identifies price divergences between spot crypto exchanges and Polymarket contracts, calculates spread opportunities, and generates trade signals on 15-minute intervals.'
Include natural keyword variations users might use, such as 'arbitrage', 'prediction market', 'price discrepancy', 'spread trading', or 'crypto arb'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (crypto trading) and a specific strategy (spot vs Polymarket divergence trading on 15-minute markets), but does not list concrete actions like 'identify divergences', 'place trades', 'calculate spreads', etc. | 2 / 3 |
Completeness | Describes a rough 'what' (divergence trading between spot and Polymarket) but completely lacks a 'when should Claude use it' clause. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and the 'what' itself is also weak, so this scores a 1. | 1 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'Polymarket', 'divergence trading', 'crypto', and '15-minute', but misses common variations users might say such as 'prediction markets', 'arbitrage', 'price discrepancy', 'spot price', or specific crypto asset names. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of 'Spot vs Polymarket divergence trading' on '15-minute crypto markets' is highly specific and niche, making it very unlikely to conflict with other skills. | 3 / 3 |
Total | 8 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, concise skill that clearly defines a divergence trading strategy with good command-line interface documentation and compact reference tables. Its main weaknesses are the lack of executable implementation code (the algorithm is described but not shown as runnable code) and missing validation/error-handling steps for what is essentially a financial trading workflow with real risk.
Suggestions
Add validation checkpoints to the workflow: what happens when the Gamma API is unreachable, when spot data is stale beyond threshold, or when a trade submission fails? Include explicit error recovery steps.
Provide at least a minimal executable code snippet showing the core detection loop (spot price lookup, divergence calculation, signal generation) rather than just the algorithmic description.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every section is lean and informative. No unnecessary explanations of what Polymarket or Binance are, no padding about crypto trading basics. The threshold table and exit logic are presented as compact references. Every token earns its place. | 3 / 3 |
Actionability | The CLI commands are concrete and copy-paste ready, and the detection algorithm is clearly described. However, there's no executable code for the actual detection/trading logic, no API connection examples, and the algorithm description is more of a specification than executable guidance. The strategy is described but not implemented in a runnable way. | 2 / 3 |
Workflow Clarity | The detection algorithm steps are sequenced, and exit logic has clear priority ordering. However, there are no validation checkpoints — no guidance on what to do if the Gamma API is down, if spot data is stale, or how to verify signals before acting. For a trading system involving real money, missing error recovery and validation caps this at 2. | 2 / 3 |
Progressive Disclosure | For a skill under 50 lines, the content is well-organized with clear sections (Quick Start, Commands, Detection Algorithm, Threshold Buckets, Exit Logic). The structure allows quick scanning and progressive depth without needing external files. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- alsk1992/CloddsBot
- Commit
e71a5f6
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.