crypto-derivatives

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

Quality

58%

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

50%

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

The body is a thorough, well-organized reference with concrete strategy parameters, but it is monolithic and re-teaches concepts Claude already knows without progressive disclosure or operational validation steps. Splitting content into references and trimming educational filler would improve conciseness and disclosure.

Suggestions

Trim explanations of well-known concepts (basic Greeks, contango/backwardation definitions, funding-rate sign rules) to reduce token cost and assume Claude's competence.

Move the perp, term-structure, and options sections into separate referenced files (e.g., references/perps.md) with a concise overview in SKILL.md, enabling one-level-deep progressive disclosure.

Add executable, import-complete code examples (e.g., import pandas) and explicit validate-then-proceed checkpoints for any live/trade workflows.

Dimension	Reasoning	Score
Conciseness	Mostly efficient tables and one code block, but ~280 lines re-explain concepts Claude already knows (basic Greeks definitions, what contango/backwardation mean, funding-rate direction rules), which adds unnecessary tokens.	2 / 3
Actionability	Concrete thresholds, strike/delta/expiry parameters, a decision tree, and an output template give specific guidance, but only one partial Python function is executable and it references pandas (`pd`) without importing it.	2 / 3
Workflow Clarity	A decision tree and output format provide some sequence, but this reads as a reference encyclopedia rather than an operational workflow and lacks validation/feedback checkpoints for the destructive/batch operations it describes.	2 / 3
Progressive Disclosure	The file is a monolithic ~280-line document with no bundle files, external references, or navigation signaling; the three strategy domains could be split into separate reference files but are all inline.	2 / 3
	Total	8 / 12 Passed

Description

67%

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 occupies a clear, distinctive niche, but it lacks an explicit "Use when" trigger clause and relies on technical jargon over natural user phrasing. Adding trigger terms and a usage clause would raise the weaker dimensions.

Suggestions

Add an explicit 'Use when...' clause naming natural user triggers (e.g., 'Use when analyzing crypto perpetual funding rates, futures basis/term structure, or BTC/ETH options volatility and Greeks').

Soften jargon with common phrasings users would actually say, such as 'futures curve', 'options implied volatility', or 'funding rate arbitrage' alongside contango/backwardation terminology.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: "perpetual funding-rate arbitrage, futures term-structure contango/backwardation trading, and option volatility-smile / Greeks analysis" — three distinct, concrete strategy families rather than vague language.	3 / 3
Completeness	It clearly states what the skill does but provides no "Use when..." clause or equivalent explicit trigger guidance, which per the rubric caps completeness at 2.	2 / 3
Trigger Term Quality	Domain terms like "contango/backwardation" and "volatility-smile / Greeks" are relevant but lean toward technical jargon and omit common lay variations a user would naturally say; no explicit user-facing trigger phrasing.	2 / 3
Distinctiveness Conflict Risk	The crypto-derivatives niche (funding arbitrage, term-structure, options Greeks) is specific and clearly distinct from other skills, making wrong-skill triggering unlikely.	3 / 3
	Total	10 / 12 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: 8643fcd

Reviewed: 2 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.