CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

risk-analysis

Risk measurement and stress testing — VaR/CVaR/max drawdown calculation, Monte Carlo simulation, extreme-value tail-risk analysis, and historical scenario stress testing.

Quality

74%

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/risk-analysis/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 dense, largely executable reference whose strongest material is the module-specific calibration knowledge (sign conventions, tail classification thresholds, reproducibility rules) that Claude could not reconstruct. It is held back by inline textbook background, a formula-only stress-testing section, and a monolithic structure with no progressive disclosure into reference files.

Suggestions

Trim or drop the textbook passages Claude already knows (VaR/CVaR definitions, method advantages/disadvantages table, skewness/kurtosis explanations, Basel note) and keep only the module-specific behavior.

Make the stress-testing workflow executable like the rest: expose or reference a function that applies STRESS_SCENARIOS shocks to positions instead of leaving a Σ formula for inline retyping.

Split the scenario tables, the EVT/GPD deep-dive, and the report template into one-level-deep reference files (e.g. references/scenarios.md, references/evt.md) linked from a leaner SKILL.md.

DimensionReasoningScore

Conciseness

Mostly efficient — sign conventions, the parametric-vs-historical calibration table, the 2σ tail_type rule, and seed discipline are genuinely non-obvious — but it also explains concepts Claude already knows: VaR/CVaR definitions, the three-method advantages/disadvantages table, skewness/kurtosis meanings, and the Basel II/III row. Not 2: the padding is embedded and brief rather than dominating; not 4: several textbook passages could be cut outright.

3 / 5

Actionability

An executable import block, concrete call signatures with defaults, and documented return keys make most sections copy-paste ready (e.g. `historical_var(returns, confidence=0.95)`, `fit_gpd_tail(returns, threshold_pct=5.0)`). Not 5: the stress-testing section — a headline capability — provides only a formula (`portfolio_loss = Σ(weight_i × shock_i × position_i)`) and a scenario dict with no callable function, unlike every other section.

4 / 5

Workflow Clarity

The Analysis Steps give a clear 7-step sequence with explicit checkpoints such as "If you ever compute a CVaR below its VaR, the tail mask is wrong" and "Check that shape_xi is stable across a few nearby threshold_pct values". Not 5: there is no validate→fix→retry feedback loop and some checkpoints (e.g. stress-test adequacy assessment) are left implicit; not 3: several concrete validation checks are explicitly stated.

4 / 5

Progressive Disclosure

The body is well-headered and navigable, but it is a ~310-line monolith with no bundle files at all: the historical/hypothetical scenario tables, the GPD/EVT deep-dive, and the output template are inline content that would sit better in one-level-deep reference files. Not 4: a skill of this size has clear separable material; not 2: section structure is good, not minimal.

3 / 5

Total

14

/

20

Passed

Description

75%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 specific, well-scoped description of the risk-measurement domain with strong, natural trigger terms and minimal conflict risk. Its one material weakness is the complete absence of a "when to use" clause, which caps completeness and leaves invocation guidance implicit.

Suggestions

Append an explicit trigger clause, e.g. "Use when asked to quantify portfolio or backtest risk: VaR/CVaR, drawdown, stress tests, or tail-risk analysis."

Add natural synonyms users say, such as "value at risk" and "expected shortfall", alongside the abbreviations to broaden trigger coverage.

State the intended context (evaluating backtest results, setting risk limits for allocation) in the description so the "when" is explicit rather than inferable.

DimensionReasoningScore

Specificity

"VaR/CVaR/max drawdown calculation, Monte Carlo simulation, extreme-value tail-risk analysis, and historical scenario stress testing" lists four-plus specific concrete actions that comprehensively cover the risk-measurement domain. Not 4: the action list is comprehensive rather than having minor gaps.

5 / 5

Completeness

The "what" is clear and concrete (calculation, simulation, and stress-testing capabilities), but there is no "Use when..." clause or any equivalent explicit trigger guidance, capping completeness at 3 per the rubric guideline. Not 4: the "when" is entirely absent, not merely implicit.

3 / 5

Trigger Term Quality

Terms a user would naturally say are present ("risk", "stress testing", "VaR", "drawdown", "Monte Carlo", "tail-risk"), giving good keyword coverage. Not 5: common variations and synonyms are missing, e.g. "value at risk" spelled out, "expected shortfall", or a plain-language phrase like "how much could this portfolio lose".

4 / 5

Distinctiveness Conflict Risk

Technique-specific terms (VaR/CVaR, max drawdown, Monte Carlo, extreme-value tail analysis, stress testing) carve out a clear quantitative-risk niche with distinct triggers and minimal conflict risk against adjacent skills. Not 4: no plausible overlapping skill would claim these exact triggers.

5 / 5

Total

17

/

20

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.

Validation — 15 / 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

Path

agent/src/skills/risk-analysis/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.