CtrlK
BlogDocsLog inGet started
Tessl Logo

correlation-regime

Correlation-regime detection and crisis attribution — edge-density regime states with hysteresis, causal (no look-ahead) smoothing, regime-aware exposure context, first-mover crisis attribution with honest NAME / MACRO / AMBIGUOUS / ABSTAIN verdicts, and a correlation-rewiring leaderboard that catches slow bleed-outs

61

Quality

77%

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/correlation-regime/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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, highly actionable body: four executable implementations with edge-case guards, concrete threshold calibration guidance, explicit causality and calibration discipline, and a clear output template. Its weaknesses are repetition — the not-a-trade-signal and unpublished-provenance caveats are each restated three to four times — and modest missing validation checkpoints in the mode workflows despite otherwise excellent structure and one-level-deep external references.

Suggestions

State the 'not a trade signal' disclaimer once (Overview or Notes) and reference it elsewhere with a single clause instead of restating it in Mode 2, the output template, and Notes.

Consolidate the unpublished-internal-replays provenance caveat into the Overview and cut its restatements in Mode 3 and References to a one-line pointer.

Add an explicit verification step to each mode workflow (e.g. 'confirm the calm-period false-alarm rate before quoting regime counts', 're-check onset lead times after replacing filters with causal versions' as a numbered step) to close the validation gaps.

DimensionReasoningScore

Conciseness

The body is dense with executable code, calibration tables, and non-obvious domain warnings, but it repeats the same caveats multiple times — the 'not a trade signal' disclaimer appears in the Overview, Mode 2, the output template, and Notes; the unpublished-replay provenance caveat is restated in the Overview, Mode 3, and References — fitting the level-3 anchor 'mostly efficient but includes some unnecessary explanation or could be tightened'. It is not a 2 because there is no padding explaining concepts Claude already knows, and not a 4 because the redundant disclaimer repetition is more than a minor trim.

3 / 5

Actionability

Four complete, copy-paste-ready Python functions with docstrings, argument definitions, edge-case guards (exit_threshold validation, MAD-zero handling, min_bars checks), a concrete threshold-selection table, a pip install command, and a full output report template — matching the level-5 anchor of fully executable guidance with specific examples covering the common cases. Not a 4 because no key execution detail is missing.

5 / 5

Workflow Clarity

Each mode opens with a numbered workflow (e.g. Mode 1's five steps from rolling correlations through hysteresis to emitting regime state) followed by implementing code, and the Notes plus 'Calibration Discipline' sections supply checkpoints like walk-forward label selection and 'quote the calm-period false-alarm rate as the honesty metric'. This fits the level-4 anchor 'clear sequence with most checkpoints present; minor validation gaps' — it is not a 5 because the mode workflows lack explicit validate-and-verify steps for outputs (e.g. no stated step for checking regime output or false-alarm rate before reporting), though nothing here is destructive or batch, so no cap applies.

4 / 5

Progressive Disclosure

The body is well organized into a clear Overview, four mode sections each with use case, workflow, code, and calibration notes, plus Dependencies, Output Format, Notes, and References — with the deep material (pipeline math, pinned regression) correctly deferred one level deep to an external repo and sibling skills. This fits the level-4 'good structure; most content appropriately placed; references mostly clear; minor organization gaps' anchor. It is not a 5 because ~250 lines of inline function code and the long provenance narrative could live in reference files, and not a 3 because navigation is easy and nothing that belongs in a nested reference is buried.

4 / 5

Total

16

/

20

Passed

Description

71%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 highly specific, capability-dense description that clearly and comprehensively states what the skill does, written in appropriate non-second-person voice. Its main weakness is the complete absence of an explicit 'Use when...' trigger clause, which both caps completeness and leaves the 'when to invoke' decision to inference; a secondary weakness is mild keyword overlap with plain correlation analysis.

Suggestions

Append an explicit trigger clause, e.g. 'Use when the user asks about correlation regimes, market fusing into one bloc, crisis triggers or who moved first, diversification breakdown, or slow bleed-outs — not for static pair correlation (see correlation-analysis).'

Add a few natural user phrasings as trigger terms — 'how correlated', 'market stress', 'diversification breakdown', 'who moved first' — to broaden keyword coverage.

Sharpen the contrast with the sibling correlation-analysis skill in one short clause so a simple pair-correlation request does not trigger this skill.

DimensionReasoningScore

Specificity

The description enumerates multiple concrete capabilities — 'edge-density regime states with hysteresis, causal (no look-ahead) smoothing, regime-aware exposure context, first-mover crisis attribution with honest NAME / MACRO / AMBIGUOUS / ABSTAIN verdicts, and a correlation-rewiring leaderboard' — which matches the level-5 anchor of multiple specific concrete actions with comprehensive coverage. It is not a 4 because coverage of the skill's four modes is complete rather than having minor gaps, and not lower because no part of it is generic padding.

5 / 5

Completeness

The 'what' is explicit and detailed, but there is no 'Use when...' clause or equivalent explicit trigger guidance — the 'when' is only weakly implied by the capability list. Per the judging guideline, a missing 'Use when...' clause caps completeness at 3, which fits the anchor 'Has a clear what but when is missing or only weakly implied'.

3 / 5

Trigger Term Quality

It carries solid natural keywords — 'correlation', 'regime', 'crisis attribution', 'exposure', 'rewiring leaderboard' — a user would plausibly say, matching the level-4 'good keyword coverage; a few natural terms missing' anchor. It is not a 5 because common user phrasings like 'how correlated', 'market stress', 'diversification breakdown', or 'who moved first' are absent, and not a 3 because the terms present are natural rather than jargon-only.

4 / 5

Distinctiveness Conflict Risk

The niche is distinct — 'correlation-regime detection and crisis attribution' with named verdict categories — but the bare word 'correlation' overlaps with a generic correlation-analysis skill the skill itself acknowledges as a sibling, creating minor overlap risk when a user asks a simple correlation question. This fits the level-4 'mostly distinct; minor overlap risk with closely related skills' anchor rather than 5 (no meaningful conflict) or 3 (broad overlap).

4 / 5

Total

16

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (505 lines); consider splitting into references/ and linking

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

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.