crypto-derivatives

Crypto-derivatives strategies — perpetual funding-rate arbitrage, futures term-structure contango/backwardation trading, and option volatility-smile / Greeks analysis.

Quality

64%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./agent/src/skills/crypto-derivatives/SKILL.md

Quality

Content

42%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 delivers genuinely useful crypto-specific content — thresholds, parameter suggestions, a decision tree, and an output template — but buries it in textbook derivatives explanations and non-executable snippets, all in one monolithic file. Trimming known concepts and splitting reference material into bundle files would substantially raise the score.

Suggestions

Delete or drastically compress sections explaining concepts Claude already knows (Basic Greeks table, contango/backwardation definitions, funding-payment mechanics), keeping only the crypto-specific deltas like 'BTC IV is often 50-120%' and 'crypto trades 7x24'.

Make the term-structure snippet executable: import pandas, show how prices are fetched, or explicitly label it as an illustrative formula and provide a runnable script in scripts/.

Move detailed reference material (strategy parameter tables, exchange comparison, historical regularities, output template) into references/*.md files and link them one level deep from SKILL.md.

Dimension	Reasoning	Score
Conciseness	A large fraction of the body restates textbook knowledge Claude already has: the funding mechanism ('longs pay shorts'), 'Contango: far month > near month > spot', and a full Basic Greeks table defining Delta/Gamma/Theta/Vega. The crypto-specific specifics (settlement times, IV bands, thresholds) are the real value, but several sections are unnecessary explanation, matching 'noticeably verbose' rather than 'mostly efficient'.	2 / 5
Actionability	Concrete elements exist — funding-rate signal bands, strategy parameter tables ('Strike: 10-15% below spot', 'IV > 80% consider selling'), a decision tree, and an output template. But the sole code sample is illustrative rather than executable (uses pd.Timestamp without importing pandas, no data retrieval), and data acquisition is hand-waved ('available through the OKX data source'), so guidance is incomplete rather than copy-paste ready.	3 / 5
Workflow Clarity	The Analysis Framework section sequences the work (monitoring metrics → market-environment judgment via decision tree → strategy selection → output format), which is a coherent flow. However, the steps from raw data to the output table are implicit, and there are no validation checkpoints (e.g., verifying fetched prices or sanity-checking computed basis), matching 'sequence present but checkpoints missing'.	3 / 5
Progressive Disclosure	The body has a clear section hierarchy (perpetuals, term structure, options, framework, output) but is a single ~280-line file with no bundle at all, so detailed reference material (strategy parameter tables, exchange characteristics, the output template) that belongs in separate files is inlined. Structure exists, but the split is not made.	3 / 5
	Total	11 / 20 Passed

Description

70%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.

A strong, domain-specific description with good trigger vocabulary and clear niche identity. Its main defect is the complete absence of a 'when to use' clause, which both caps completeness and leaves the activation context implicit.

Suggestions

Append an explicit trigger clause, e.g. 'Use when the user asks about perpetuals, funding rates, futures basis, contango/backwardation, or crypto options IV/Greeks.'

Add natural synonyms users actually say — 'perp', 'basis trade', 'IV', 'options skew' — to broaden trigger coverage.

State the deliverable (e.g., 'produces a market snapshot and strategy suggestion table') so the 'what' covers the output, not just the topic areas.

Dimension	Reasoning	Score
Specificity	The description names the domain and lists several concrete capability areas — 'perpetual funding-rate arbitrage, futures term-structure contango/backwardation trading, and option volatility-smile / Greeks analysis' — which are specific strategy types, not vague claims. It falls short of 5 because these read as topic labels rather than fully enumerated concrete actions, with minor coverage gaps (e.g., no mention of analysis output or exchanges).	4 / 5
Completeness	The 'what' is clearly stated (three strategy directions), but there is no 'Use when...' clause or equivalent explicit trigger guidance anywhere in the description, which caps completeness at 3 per the judging guidelines. It is not a 2 because the 'what' half is concrete and well-scoped.	3 / 5
Trigger Term Quality	Natural terms a user would say are present: 'crypto-derivatives', 'perpetual', 'funding-rate arbitrage', 'contango/backwardation', 'Greeks'. A few common variations are missing (e.g., 'perp', 'basis trade', 'IV', 'options skew'), keeping it below the comprehensive-synonym anchor at 5.	4 / 5
Distinctiveness Conflict Risk	The crypto-derivatives niche is tightly defined by distinct technical triggers (perpetuals, funding rates, term structure, Greeks), minimizing overlap with generic crypto-trading or TradFi derivatives skills. It is not a 4 because the specialized vocabulary makes wrong-skill triggering very unlikely.	5 / 5
	Total	16 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: HKUDS/Vibe-Trading
Path: agent/src/skills/crypto-derivatives/SKILL.md
Commit: 251b094

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.