CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

risk-metrics-calculation

Calculate portfolio risk metrics including VaR, CVaR, Sharpe, Sortino, and drawdown analysis. Use when measuring portfolio risk, implementing risk limits, or building risk monitoring systems.

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 ./plugins/quantitative-trading/skills/risk-metrics-calculation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

43%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 body is well-structured as a progressive-disclosure overview with a clean, verified pointer to the real details file, and it is token-lean. However, it functions as a concept glossary rather than an actionable guide: no executable code, formulas, or metric-computation workflow appears in the body, and parts restate finance knowledge Claude already has.

Suggestions

Add a minimal worked example or the core formulas inline (e.g., a short historical-VaR snippet or Sharpe/Sortino formulas) so the skill is actionable before opening references/details.md.

Include a short numbered workflow for a typical risk-metrics task (gather return series → pick horizon and lookback → compute metrics → sanity-check against known benchmarks) with a validation checkpoint.

Trim or collapse the 'Core Concepts' category table and 'Time Horizons' block, which restate standard finance knowledge Claude already has, in favor of the actionable content above.

DimensionReasoningScore

Conciseness

The body is short and scannable, but the "Risk Metric Categories" table and the "Time Horizons" block restate standard finance knowledge Claude already has (what Std Dev/Beta/VaR are, which horizon suits which purpose). This matches anchor 3 ("mostly efficient but includes some unnecessary explanation"); it is not a 4 because both Core Concepts sections could be cut or collapsed with little loss.

3 / 5

Actionability

The body contains no code, formulas, or commands — no VaR estimation method (historical vs. parametric), no Sharpe/Sortino formulas, nothing executable. Guidance like "Stress test - Historical and hypothetical" and "Don't use short lookbacks" is high-level direction, matching anchor 2 ("minimal concrete guidance; high-level hints but missing the specific steps to execute"). It is not a 3 because there is not even partial executable content inline — all concrete material is deferred to references/details.md.

2 / 5

Workflow Clarity

No sequence is provided for actually computing or validating metrics (e.g., gather returns → choose lookback/horizon → compute → sanity-check); the only sequencing is the conditional "Read that file when the navigation tier above is insufficient." This matches anchor 2 ("rough sequence present but many gaps; steps poorly defined; validation absent"). It is not a 1 because the sections do imply a loose order (when-to-use → concepts → details → best practices), and not a 3 because there are no checkpoints or decision guidance for metric selection at all.

2 / 5

Progressive Disclosure

The body is a concise overview with a single, clearly signaled, one-level-deep reference: "Detailed pattern documentation lives in `references/details.md`. Read that file when the navigation tier above is insufficient" — verified to exist (496 lines of worked patterns) with no nested .md references. Content is appropriately split between overview and detail file, matching the anchor-5 structure.

5 / 5

Total

12

/

20

Passed

Description

92%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: it pairs a concrete, metric-enumerated capability statement with an explicit 'Use when...' clause containing natural trigger phrases. The only weakness is slightly thin synonym coverage (e.g., 'Value at Risk', 'expected shortfall', 'Sharpe ratio' as separate triggers).

DimensionReasoningScore

Specificity

"Calculate portfolio risk metrics including VaR, CVaR, Sharpe, Sortino, and drawdown analysis" lists multiple specific concrete actions (five named metrics plus drawdown analysis) with comprehensive coverage of the domain, matching the anchor-5 example's breadth. It is not a 4 because the coverage has no meaningful gaps — the named metrics span tail risk, risk-adjusted returns, and drawdown.

5 / 5

Completeness

It explicitly answers both: what ("Calculate portfolio risk metrics including VaR, CVaR, Sharpe, Sortino, and drawdown analysis") and when ("Use when measuring portfolio risk, implementing risk limits, or building risk monitoring systems") with concrete trigger phrases. This directly matches the anchor-5 good example structure.

5 / 5

Trigger Term Quality

"measuring portfolio risk", "implementing risk limits", "building risk monitoring systems" are natural phrases users would say, giving good keyword coverage. It is not a 5 because common variations are missing — the spelled-out "Value at Risk", "expected shortfall" (vs. only CVaR), and "Sharpe ratio" as a standalone trigger.

4 / 5

Distinctiveness Conflict Risk

The quant-finance risk-metrics niche (VaR, CVaR, Sortino, drawdown) with distinct triggers like "implementing risk limits" is clearly distinguishable from general finance or portfolio-construction skills. Not a 4: the specific metric names and trigger phrases leave minimal overlap risk with adjacent skills.

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

wshobson/agents

Path

plugins/quantitative-trading/skills/risk-metrics-calculation/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.