CtrlK
BlogDocsLog inGet started
Tessl Logo

crypto-derivatives

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

57

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

63%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 well-structured and provides concrete parameters and one executable code snippet, but it pads in basic concepts Claude already knows and keeps all three strategy directions inlined in a single file without external references. Trimming known concepts and splitting the three directions into reference files would improve both conciseness and progressive disclosure.

Suggestions

Remove or condense explanations of basic concepts Claude already knows (basic Greeks, how funding rates anchor to spot, contango/backwardation definitions) and keep only the crypto-specific parameters and thresholds.

Split the three strategy directions into separate reference files (e.g. references/perpetual.md, references/term-structure.md, references/options.md) and keep SKILL.md as a concise overview with signaled links.

Provide executable code or concrete command examples for the option strategies (short straddle, protective put, iron butterfly) instead of prose-only descriptions.

DimensionReasoningScore

Conciseness

Dense and largely useful, but it explains concepts Claude already knows (basic Greeks definitions, how funding rates anchor to spot, contango/backwardation basics), placing it at 'mostly efficient but includes some unnecessary explanation'.

3 / 5

Actionability

Provides a real executable Python function, specific numeric parameter thresholds, a decision tree, and an output template, but most option strategies are described in prose rather than copy-paste-ready code, matching 'mostly executable guidance with minor gaps'.

4 / 5

Workflow Clarity

The Strategy Selection Decision Tree and Daily Monitoring Metrics give a clear sequenced procedure for a non-destructive research skill; it stops short of 5 because there are no explicit validation or error-recovery checkpoints.

4 / 5

Progressive Disclosure

No bundle files exist and the body is a single ~274-line inlined document; it has clear section headers but content that could be split into separate reference files (perpetual, term-structure, options) is kept inline, matching the 'some structure but could be better organized' anchor.

3 / 5

Total

14

/

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.

The description clearly and specifically names what the skill covers across three crypto-derivatives strategy directions, but it omits any explicit 'when to use' trigger guidance. Adding a 'Use when...' clause would lift the capped completeness score.

Suggestions

Add an explicit 'Use when...' trigger clause, e.g. 'Use when analyzing crypto-derivatives, funding rates, futures basis, or option Greeks/volatility.'

Include more natural user-facing synonyms (e.g. 'funding rate', 'perpetual futures', 'options', 'IV', 'basis trading') alongside the technical jargon to improve trigger-term naturalness.

DimensionReasoningScore

Specificity

Lists three concrete strategy directions with specific sub-techniques ('perpetual funding-rate arbitrage', 'futures term-structure contango/backwardation trading', 'option volatility-smile / Greeks analysis'), matching the 'several specific actions; minor gaps' anchor rather than the comprehensive 5.

4 / 5

Completeness

The 'what' is clearly stated but there is no 'Use when...' clause or equivalent trigger guidance, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

Good domain keyword coverage (crypto-derivatives, funding-rate, contango/backwardation, volatility-smile, Greeks) but largely technical jargon with a few natural user phrasings and synonyms missing, so it sits at 4 rather than the comprehensive 5.

4 / 5

Distinctiveness Conflict Risk

The crypto-derivatives niche with its three named sub-strategies is clearly distinguishable and unlikely to trigger for the wrong skill, matching the 'clear niche with distinct triggers; minimal conflict risk' anchor.

5 / 5

Total

16

/

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
HKUDS/Vibe-Trading
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.