CtrlK
BlogDocsLog inGet started
Tessl Logo

divergence

Spot vs Polymarket divergence trading on 15-minute crypto markets

62

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./src/skills/bundled/divergence/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

83%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is concise, actionable, and well-structured with copy-paste commands and concrete formulas. Its main gap is the absence of validation/verification checkpoints for a destructive batch financial operation, which caps workflow clarity at 3.

Suggestions

Add an explicit validation checkpoint before live trading, e.g. confirm dry-run results, verify account/balance and market freshness, then re-confirm before switching off --dry-run.

Include a feedback loop for order failures (detect rejection/stale market → skip or retry) to support the batch trading workflow.

Consider moving the Threshold Buckets table and full Exit Logic into a short reference file to keep the overview even leaner, though the current inline placement is already reasonable.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence: it explains the strategy in two sentences, gives the tag encoding once, and uses compact tables and command blocks without padding or explaining what Binance/crypto/Polymarket are.

5 / 5

Actionability

It provides copy-paste-ready commands covering common cases ('/div start BTC,ETH --size 30', '/div config --tp 20 --sl 30'), a concrete detection formula with binary search, and explicit exit-logic percentages — fully executable guidance.

5 / 5

Workflow Clarity

Sequences exist (detection algorithm steps 1-3, numbered exit logic), but this skill places real financial orders across multiple markets in batch and has no validation/verification checkpoints or error-recovery feedback loops before going live, so the destructive/batch cap of 3 applies.

3 / 5

Progressive Disclosure

Content is well organized into clearly labeled sections (Quick Start, Commands, Detection Algorithm, Threshold Buckets, Exit Logic) in a single self-contained file with no nested references; it is appropriately placed though a compact reference could offload the buckets/exit tables.

4 / 5

Total

17

/

20

Passed

Description

65%Weight 40%Scale 1-5

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 is specific and distinctive with good trigger terms, but lacks an explicit 'Use when...' trigger clause, capping its completeness. Adding a brief usage-trigger sentence would lift it from a mid-tier to a strong description.

Suggestions

Append a 'Use when...' clause, e.g. 'Use when the user wants to trade spot-vs-Polymarket price lag or asks about crypto divergence/arbitrage on short-window markets.'

Name 1-2 more concrete actions (e.g. 'detects price lag, buys the lagging side, exits on correction') to raise specificity from 3 toward 5.

Add natural synonyms such as 'price lag' or 'arbitrage' alongside 'divergence' to broaden trigger coverage.

DimensionReasoningScore

Specificity

The description names the domain ('divergence trading') and one concrete action on a specific market type ('15-minute crypto markets'), but does not list multiple concrete actions like detecting lag, buying the lagging side, or exiting, so it is not comprehensive.

3 / 5

Completeness

It gives a clear 'what' (divergence trading on 15-minute crypto markets) but has no 'Use when...' clause or explicit trigger guidance, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

It includes natural trader-facing terms ('divergence trading', 'Polymarket', 'spot', '15-minute crypto markets') that a user would plausibly say, though synonyms like 'price lag' or 'arbitrage' are missing.

4 / 5

Distinctiveness Conflict Risk

The niche is highly specific (spot vs Polymarket price-lag divergence on 15-minute crypto binary markets), making it clearly distinguishable with minimal conflict risk against other skills.

5 / 5

Total

15

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
alsk1992/CloddsBot
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.