CtrlK
BlogDocsLog inGet started
Tessl Logo

stablecoin-flow

Stablecoin supply and flow analysis — USDT/USDC mint-burn signals, exchange stablecoin reserves, on-chain stablecoin velocity, and capital rotation indicators for crypto market timing.

62

Quality

73%

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

Fix and improve this skill with Tessl

tessl review fix ./agent/src/skills/stablecoin-flow/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%

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

The body is highly actionable with concrete code, thresholds, and a clear output template, but it is verbose in places and monolithic — no content is split into reference files. Adding an explicit analysis workflow and offloading detail to references would improve clarity.

Suggestions

Add an explicit numbered workflow (gather data → compute per-dimension signals → composite score → produce output) with validation checkpoints.

Move detailed per-signal code and the data-sources table into reference files, keeping SKILL.md a lean overview.

Trim conceptual prose (e.g. the 'dry powder' metaphor and mint/burn basics) that Claude already knows.

DimensionReasoningScore

Conciseness

Dense with valuable specialized thresholds and interpretive tables, but it also explains concepts Claude largely knows (the 'dry powder' metaphor, what minting/burning signals) and carries heavy code comments that could be tightened.

2 / 3

Actionability

Provides concrete executable Python functions with specific numeric thresholds, interpretive tables, a data-sources table, and a copy-paste output template — well beyond abstract direction.

3 / 3

Workflow Clarity

The output template and per-dimension signals imply a sequence, but there is no explicitly numbered workflow with checkpoints tying data-gathering to signal computation to the composite output.

2 / 3

Progressive Disclosure

Well-sectioned and self-contained, but ~245 lines of methodology, per-signal code, and data sources all live inline with no reference files to offload detail, matching the anchor of content that could be separate being inline.

2 / 3

Total

9

/

12

Passed

Description

82%

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 four concrete signal categories with natural trigger terms, but it omits an explicit 'Use when...' clause, which caps completeness. Adding explicit usage triggers would round it out.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when analyzing stablecoin capital flows, mint/burn events, exchange reserves, or crypto market liquidity timing.'

Broaden trigger coverage with common user phrasings such as 'dry powder', 'stablecoin reserves', or 'capital rotation'.

DimensionReasoningScore

Specificity

Lists multiple specific concrete capabilities — 'USDT/USDC mint-burn signals, exchange stablecoin reserves, on-chain stablecoin velocity, and capital rotation indicators' — rather than vague language.

3 / 3

Completeness

Clearly states what the skill does, but there is no explicit 'Use when...' trigger clause; the trailing 'for crypto market timing' only implies when to use it, which caps completeness at 2 per the guideline.

2 / 3

Trigger Term Quality

Includes natural terms a crypto user would say — 'stablecoin', 'USDT/USDC', 'mint-burn', 'crypto market timing' — giving good coverage of likely phrasings.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche (stablecoin flow analysis) with distinct terminology unlikely to overlap or conflict with other skills.

3 / 3

Total

11

/

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.