CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

crypto-regime-analyzer

Quantifies crypto market regime health using free, keyless public data (CoinGecko + Binance funding). Generates a 0-100 composite score across 6 components (100 = risk-on) with a posture recommendation. No API key required. Use when user asks about crypto market conditions, whether it's alt season, BTC dominance, crypto risk-on vs risk-off, funding rates, or whether crypto exposure should be increased or reduced.

Quality

94%

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

86%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.

A strong, well-structured body: executable commands with documented flags, a clearly sequenced three-phase workflow with explicit degraded-data checkpoints, and clean progressive disclosure verified against the real bundle. The only flaws are a Phase 2 / Output redundancy and a recovery path documented outside the workflow sequence.

Suggestions

Collapse the artifact descriptions in Phase 2 and the Output section into one place (e.g., keep the detail in Output and have Phase 2 just say 'interpret the two artifacts described below') to remove the duplicated file/summary listing.

Fold the dominance-history recovery step into Phase 1 or 2 as an explicit conditional (e.g., 'if the dominance component reports data_available: false and you have a prior snapshot, re-run with --input-json to seed it') so the validate/fix/retry loop is part of the workflow itself.

DimensionReasoningScore

Conciseness

Efficient overall — assumes Claude's competence (no explanations of what funding rates or DMA crossovers are), dense component/zone tables, and a genuinely useful Known Limitations section. Not anchor 5 because of a redundancy: Phase 2 ('The script writes crypto_regime.json... and crypto_regime.md... and prints a one-line summary') repeats material restated almost verbatim in the Output section. Not anchor 3 since the padding is limited to this one overlap.

4 / 5

Actionability

Fully executable: exact copy-paste commands for both live and offline modes ('python3 skills/crypto-regime-analyzer/scripts/crypto_regime_analyzer.py --output-dir reports/<routine-or-date>'), flags with defaults documented ('--top-n <int> universe size (default 20), --cache-dir <path>... --quiet'), exact output filenames, enumerated JSON fields, and a sample console output line. Covers the common cases completely.

5 / 5

Workflow Clarity

Clear three-phase sequence with an explicit interpretation checkpoint ('Flag any components reporting data_available: false and what that means for confidence') and degraded-mode behavior documented. Not anchor 5 because the error-recovery path for the one long-running gap ('Seed it faster via --input-json' for the 31-observation dominance requirement) sits in Known Limitations rather than being integrated into the workflow as a validate/fix/retry loop; not anchor 3 because the checkpoints that do exist are explicit, and the operation is read-only analysis rather than destructive/batch.

4 / 5

Progressive Disclosure

Clear overview with well-signaled one-level-deep references, verified against the actual bundle: 'references/crypto_regime_methodology.md' and 'references/VALIDATION.md' exist and hold the threshold tables and evidence boundary moved out of SKILL.md, and every path in Resources (crypto_regime_analyzer.py, data_client.py, calculators/, scorer.py, tests/) is a real file with its role described. Navigation is easy and nothing that belongs in a reference is inlined.

5 / 5

Total

18

/

20

Passed

Description

100%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 exemplary: third-person voice, concrete actions with named data sources and scoring model, and an explicit 'Use when' clause covering the full natural trigger vocabulary. It is concise for its information density with no filler. No improvements needed.

DimensionReasoningScore

Specificity

Multiple concrete actions with full coverage of the skill's behavior: 'Quantifies crypto market regime health using free, keyless public data (CoinGecko + Binance funding)', 'Generates a 0-100 composite score across 6 components (100 = risk-on) with a posture recommendation' — data sources, scoring model, and output are all named. Not anchor 4 because there is no coverage gap: every top-level capability (input, transformation, output posture) is explicitly stated.

5 / 5

Completeness

Explicitly answers both questions: 'what' via 'Quantifies... Generates a 0-100 composite score across 6 components... with a posture recommendation', and 'when' via the explicit 'Use when user asks about...' clause with concrete trigger phrases. Matches the anchor-5 example pattern (what + 'Use when...' with concrete triggers); not anchor 4 since the when-clause is already fully specific.

5 / 5

Trigger Term Quality

Comprehensive natural-term coverage including synonyms: 'crypto market conditions', 'whether it's alt season', 'BTC dominance', 'crypto risk-on vs risk-off', 'funding rates', 'whether crypto exposure should be increased or reduced' — these are exactly the phrases a user would naturally say. Not anchor 4 because no common variation of the trigger vocabulary is missing.

5 / 5

Distinctiveness Conflict Risk

Clear crypto-regime niche with distinct triggers ('alt season', 'BTC dominance', 'funding rates') that no generic market-analysis skill would claim; consistently scoped as crypto throughout. Not anchor 4 because overlap with adjacent equity-regime skills is avoided by the crypto qualifier on every trigger phrase, keeping conflict risk minimal.

5 / 5

Total

20

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

tradermonty/claude-trading-skills

Path

skills/crypto-regime-analyzer/SKILL.md

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.