CtrlK
BlogDocsLog inGet started
Tessl Logo

tracking-crypto-derivatives

Track cryptocurrency futures, options, and perpetual swaps with funding rates, open interest, liquidations, and comprehensive derivatives market analysis. Use when monitoring derivatives markets, analyzing funding rates, tracking open interest, finding liquidation levels, or researching options flow. Trigger with phrases like "funding rate", "open interest", "perpetual swap", "futures basis", "liquidation levels", "options flow", "put call ratio", "derivatives analysis", or "BTC perps".

71

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

77%Weight 40%Scale 1-3

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

The content is well-structured and mostly lean, with real base commands and clear per-domain workflows. Its main weakness is actionability: a substantial fraction of documented CLI flags are absent from the actual script, making those examples non-executable, and two reference bundle files (errors.md, examples.md) are present but never surfaced.

Suggestions

Reconcile documented flags with derivatives_tracker.py's argparse: either implement --history, --alert-threshold, --changes, --divergence, --recent, --min-size, --pcr, --expiry, --quarterly, --all, --min-yield, and --output, or remove the examples that reference them.

Link references/errors.md and references/examples.md from the body (e.g., in Error Handling and Examples sections) so the existing bundle files are discoverable, or fold their content out of the inline sections to keep the split one level deep.

Verify each code block against the script before publishing so all examples are copy-paste ready.

DimensionReasoningScore

Conciseness

Body is lean and well-organized with executable command blocks; sentiment/OI interpretation tables act as decision guidance rather than padding. Not a 2 because no concept-explaining fluff and every section earns its place.

3 / 3

Actionability

Base commands (funding/oi/liquidations/options/basis/dashboard) are real, but many documented flags — --history, --alert-threshold, --changes, --divergence, --recent, --min-size, --pcr, --expiry, --quarterly, --all, --min-yield, --output — do not exist in derivatives_tracker.py's argparse, so those examples would error. Not a 3 because the examples are not copy-paste-ready; not a 1 because the core commands are concrete and executable.

2 / 3

Workflow Clarity

Each market type is a clearly sequenced single action with interpretation guidance, plus an Error Handling table mapping errors to causes/fixes. No destructive or batch operations require validation checkpoints, so the simple-skill exception applies.

3 / 3

Progressive Disclosure

Body points to references/implementation.md (one level, real file), but references/errors.md and references/examples.md exist yet are never linked from the body, and inline Output/Examples sections duplicate content that belongs in those reference files. Not a 3 because discovery of bundle files is incomplete and split is not fully clean; not a 1 because structure exists and the main reference is signaled.

2 / 3

Total

10

/

12

Passed

Description

100%Weight 40%Scale 1-3

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 strong: third-person voice, concrete capabilities, an explicit 'Use when' clause, and a rich set of natural trigger phrases. It answers both what the skill does and when to invoke it without padding.

DimensionReasoningScore

Specificity

Names several concrete actions across "futures, options, and perpetual swaps" plus "funding rates, open interest, liquidations, and comprehensive derivatives market analysis" — not vague.

3 / 3

Completeness

Explicitly answers what (track derivatives with funding/OI/liquidations) and when ("Use when monitoring derivatives markets, analyzing funding rates...").

3 / 3

Trigger Term Quality

Surfaces natural terms users would say: "funding rate", "open interest", "perpetual swap", "futures basis", "liquidation levels", "options flow", "put call ratio", "BTC perps".

3 / 3

Distinctiveness Conflict Risk

Clear crypto-derivatives niche with distinct triggers unlikely to collide with general crypto or document skills.

3 / 3

Total

12

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

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

Warning

Total

14

/

16

Passed

Repository
jeremylongshore/claude-code-plugins-plus-skills
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.