CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

73

Quality

92%

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 well-engineered skill body: executable commands, a transparent component model with weights and zones, honest limitations, and clean one-level-deep disclosure into real reference and script files. The only improvements are minor — merging the duplicated output-artifact descriptions and adding a brief failure-recovery note to the workflow.

Suggestions

Consolidate the output artifact descriptions: Phase 2 and the Output section both describe crypto_regime.json/crypto_regime.md and the console summary — state them once and cross-reference.

Add a short validation/recovery step in Phase 1 (e.g., what to do on a rate-limit timeout or partial fetch failure) to complement the documented component-level degradation behavior.

DimensionReasoningScore

Conciseness

Efficient body: dense component and zone tables, no explaining of concepts Claude already knows. Minor trimmable redundancy — the output artifacts (crypto_regime.json/md, console summary) are described in both Phase 2 and the Output section. Not 5 because of that duplicated output description; not 3 since nothing is padded or patronizing.

4 / 5

Actionability

Fully executable, copy-paste-ready commands for live and offline mode with the complete flag list (--top-n, --cache-dir, --quiet, --input-json, --output-dir), plus the expected console output format and guidance on interpreting component signal strings and data_available flags.

5 / 5

Workflow Clarity

Clear Phase 1→3 sequence with failure-mode handling documented (funding endpoint unreachable → component skipped; dominance data_available false until 31 observations), but the workflow itself lacks explicit validate/recover checkpoints (e.g., what to do if the script errors mid-run). Not capped at 3 since the operation is read-only analysis, not destructive or batch.

4 / 5

Progressive Disclosure

The body is a genuine overview: full scoring logic deferred to references/crypto_regime_methodology.md and evidence boundary to references/VALIDATION.md (verified to exist), both one level deep and clearly signaled, with a Resources section itemizing every real bundle file including per-component calculators and tests.

5 / 5

Total

18

/

20

Passed

Description

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

A strong description: third-person voice, concrete capability statement with scale and data sources, and an explicit 'Use when' clause rich in natural trigger phrases. The only minor gap is that the six components are referenced but not individually named.

DimensionReasoningScore

Specificity

Lists several specific actions ('Quantifies crypto market regime health', 'Generates a 0-100 composite score across 6 components... with a posture recommendation') with concrete detail on data sources and scale, but does not enumerate the component actions, so coverage has minor gaps.

4 / 5

Completeness

Explicitly answers both what ('Generates a 0-100 composite score across 6 components (100 = risk-on) with a posture recommendation') and when ('Use when user asks about crypto market conditions...'), with concrete trigger phrases; not score 4 territory because the 'when' clause is fully explicit rather than improvable.

5 / 5

Trigger Term Quality

Covers natural user phrasing comprehensively: 'crypto market conditions', 'alt season', 'BTC dominance', 'crypto risk-on vs risk-off', 'funding rates', 'whether crypto exposure should be increased or reduced' — exactly what a user would say when needing this skill.

5 / 5

Distinctiveness Conflict Risk

Clear crypto-regime niche with distinct triggers (CoinGecko + Binance funding, alt season, BTC dominance, risk-on/risk-off) that would not naturally collide with generic market or document skills; minimal conflict risk.

5 / 5

Total

19

/

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