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.

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

Quality

Content

57%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 skill body is actionable and well-structured with executable code and clear signal thresholds, but it is a lengthy single-file document with no progressive disclosure to deeper references and only an implicit analysis workflow.

Suggestions

Add an explicit numbered analysis workflow (e.g., 1. Pull supply/mint-burn data, 2. Compute per-dimension scores, 3. Aggregate composite, 4. Render output) with a verification/sanity-check step before emitting the report.

Move the chain-level distribution tables and data-source reference into a separate references file (e.g., references/data-sources.md) and link to it from SKILL.md to enable progressive disclosure.

Trim the opening overview paragraph and interpretive prose to the essential signal definitions to improve token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient code and threshold tables, but the opening 'dry powder' paragraph and several interpretive prose blocks (e.g., 'USDC is more regulated and institutional-oriented') could be tightened, fitting anchor 3 rather than 4.	3 / 5
Actionability	Provides concrete, executable Python functions (mint_burn_signal, exchange_reserve_signal, velocity_signal) with explicit thresholds plus a composite-score structure and output template; the gap is that data-fetching is only described via a sources table rather than shown in code, keeping it just below anchor 5.	4 / 5
Workflow Clarity	The seven numbered core concepts plus the output-format template imply a sequence, but there is no explicit step-by-step workflow or validation checkpoints; this is an analytical (non-destructive) skill so the destructive-cap does not apply, landing it at anchor 3.	3 / 5
Progressive Disclosure	No bundle files exist and all content lives inline in a >50-line monolithic SKILL.md; sections are well-organized but content that could be split into references (per-chain tables, data-source details) is inlined, matching anchor 3 rather than 4.	3 / 5
	Total	13 / 20 Passed

Description

66%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 is specific, keyword-rich, and occupies a clear niche, but it omits an explicit 'Use when…' trigger clause, which caps its completeness and slightly limits trigger-term and distinctiveness scores.

Suggestions

Append an explicit trigger clause, e.g. 'Use when the user asks about stablecoin flows, USDT/USDC mint-burn activity, exchange stablecoin reserves, or crypto liquidity/market timing.'

Reframe signal topics as concrete actions where possible (e.g., 'Tracks mint-burn events, monitors exchange reserves, computes on-chain velocity') to lift specificity toward anchor 5.

Add a few more natural user phrasings (e.g., 'dry powder', 'stablecoin inflows/outflows') to round out trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain plus several concrete signal types ('USDT/USDC mint-burn signals, exchange stablecoin reserves, on-chain stablecoin velocity, and capital rotation indicators'), but these are topics rather than actions, with only the single verb 'analysis' — comprehensive yet not the multi-action coverage of anchor 5.	4 / 5
Completeness	The 'what' is clear and detailed, but there is no 'Use when…' clause or equivalent explicit trigger guidance; 'for crypto market timing' only weakly implies the 'when', and the rubric caps completeness at 3 when that clause is missing.	3 / 5
Trigger Term Quality	Includes natural domain keywords a crypto analyst would say (USDT, USDC, mint-burn, exchange reserves, on-chain velocity, capital rotation, crypto market timing) with synonym coverage, but a few natural trigger phrasings are absent so it sits below anchor 5.	4 / 5
Distinctiveness Conflict Risk	A tight, distinctive niche (stablecoin flow) with low conflict risk; minor potential overlap with a broader crypto-market-analysis skill and the absence of an explicit trigger clause keep it just below anchor 5.	4 / 5
	Total	15 / 20 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/stablecoin-flow/SKILL.md
Commit: 1907e47

Reviewed: 1 day 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.