CtrlK
BlogDocsLog inGet started
Tessl Logo

liquidation-heatmap

Liquidation level analysis and heatmap interpretation — identify leveraged position concentration, liquidation cascades, stop-hunt zones, and use liquidation data as support/resistance signals.

52

Quality

58%

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/liquidation-heatmap/SKILL.md
SKILL.md
Quality
Evals
Security

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 skill body is rich and well-structured with concrete code, tables, and an output template, but it is verbose, relies on pseudocode-style helpers, and lacks an explicit validated workflow and progressive file split.

Suggestions

Tighten or move conceptual explanation (liquidation mechanics, cascade anatomy, exchange-level differences) into a reference file to reduce token load, since Claude already knows these basics.

Make the Python examples self-contained by defining or stubbing helper functions (e.g. estimate_long_liq_at_price) and passing price_range as a parameter.

Add an explicit numbered analysis workflow with validation checkpoints (e.g. verify data source coverage, cross-check OI changes) before producing the output.

DimensionReasoningScore

Conciseness

The ~280-line body is mostly efficient with useful tables and code, but spends tokens explaining concepts (liquidation mechanics, cascade anatomy, exchange differences) that Claude already knows and could be tightened.

2 / 3

Actionability

It provides concrete Python functions and formulas, but they depend on undefined helpers (estimate_long_liq_at_price) and an unpassed price_range variable, making them incomplete rather than copy-paste ready.

2 / 3

Workflow Clarity

Content is organized by topic with a useful before/during/after cascade guide, but there is no explicitly sequenced analysis workflow with validation checkpoints for the overall process.

2 / 3

Progressive Disclosure

It is a single monolithic file with well-organized sections but no external references, and substantial reference-style content (metrics tables, exchange comparisons) is inlined rather than split into separate files.

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 distinctive, naming multiple concrete capabilities in a clear niche. Its main weakness is the absence of an explicit 'Use when...' trigger clause and somewhat limited natural keyword coverage.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when analyzing liquidation heatmaps, forced liquidations, long/short squeezes, or leverage unwinds in crypto markets.'

Broaden trigger terms to include natural user phrases like 'forced liquidations', 'leverage', and 'long/short squeeze'.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions: 'identify leveraged position concentration, liquidation cascades, stop-hunt zones, and use liquidation data as support/resistance signals.'

3 / 3

Completeness

It clearly answers 'what' the skill does but provides no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 2 per the rubric guideline.

2 / 3

Trigger Term Quality

It includes relevant terms like 'liquidation cascades', 'stop-hunt zones', and 'heatmap', but omits common natural variations a user might say such as 'forced liquidations', 'leverage', or 'long/short squeeze'.

2 / 3

Distinctiveness Conflict Risk

It carves out a clear crypto-liquidation niche with distinct triggers, making it unlikely to fire for unrelated skills.

3 / 3

Total

10

/

12

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.