CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

59

Quality

67%

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

Quality

Content

35%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The SKILL.md body is well-structured but hollow: it provides almost no concrete guidance for the metrics named in the description, and its only detailed reference points to a file that does not exist. It reads as a template scaffold rather than an executable skill.

Suggestions

Add concrete, executable guidance — e.g. the VaR/CVaR/Sharpe formulas or a short Python snippet — so the Instructions section instructs rather than describes.

Create the referenced 'resources/implementation-playbook.md' (or fix the path; note the body uses 'resources/' while the description elsewhere implies 'references/') so progressive disclosure points to a real file.

Remove the redundant opening paragraph and generic 'Do not use this skill when' boilerplate, and replace 'Apply relevant best practices and validate outcomes' with a specific validation step (e.g. a sanity check that drawdown <= 0 or VaR/CVaR ordering holds).

DimensionReasoningScore

Conciseness

The body is short, but the opening 'Comprehensive risk measurement toolkit...' restates the description and the 'Do not use this skill when' bullets are generic boilerplate ('The task is unrelated to risk metrics calculation') that adds nothing Claude doesn't know; not a 1 because the Instructions and Resources sections are reasonably terse, but not a 3 due to the redundant intro and boilerplate exclusions.

2 / 3

Actionability

Guidance is abstract — 'Apply relevant best practices and validate outcomes', 'Provide actionable steps and verification' — with no formulas, code, or commands for any of the named metrics; this describes rather than instructs, and the referenced playbook is absent, so it does not reach the 'some concrete guidance' bar of a 2.

1 / 3

Workflow Clarity

Steps are listed (clarify goals, apply best practices, validate) but the sequence is generic with no real validation checkpoints or error-recovery feedback loops for risky financial calculations; not a 1 because a sequence exists, but not a 3 because 'validate outcomes' is implicit and unstructured.

2 / 3

Progressive Disclosure

The body signals a one-level-deep reference ('open resources/implementation-playbook.md'), but the referenced file does not exist in the bundle, so navigation is signaled yet broken; not a 1 because structure and a reference are present, but not a 3 because the referenced path is missing.

2 / 3

Total

7

/

12

Passed

Description

100%Weight 40%Scale 1-3

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 concise, third-person, and covers both what the skill does and when to use it with concrete metric names and natural triggers. It scores at the top of the scale on all four dimensions.

DimensionReasoningScore

Specificity

Lists multiple concrete, specific actions — 'VaR, CVaR, Sharpe, Sortino, and drawdown analysis' — matching the anchor for naming several specific concrete actions; not the level below because it goes well beyond naming a domain and a few actions.

3 / 3

Completeness

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 an explicit trigger clause; not a 2 because the 'when' is explicit, not merely implied.

3 / 3

Trigger Term Quality

Includes natural user-facing phrases such as 'measuring portfolio risk', 'implementing risk limits', 'building risk monitoring systems'; not a 2 because these are terms a user would plausibly say rather than generic jargon.

3 / 3

Distinctiveness Conflict Risk

Scoped to a clear niche — portfolio risk metrics — with distinct triggers unlikely to fire for unrelated skills; not a 2 because the metric list and triggers are specific enough to avoid overlapping with general finance skills.

3 / 3

Total

12

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
rmyndharis/antigravity-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.