CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

risk-manager

Monitor portfolio risk, R-multiples, and position limits. Creates hedging strategies, calculates expectancy, and implements stop-losses.

Quality

65%

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/AI-Agents-Safe-Coding-Skills/skills/risk-manager/SKILL.md

The canonical home for this skill is risk-manager in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

50%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 a reasonable overview with a clear focus-area list, a sequenced approach, and one concrete formula, but it is held back by templated boilerplate sections, mostly high-level guidance lacking executable specifics (no sizing/Kelly/VaR math), absent validation checkpoints, and a dangling reference to a nonexistent `resources/implementation-playbook.md`.

Suggestions

Remove or replace the generic "Use/Do not use this skill when" and Instructions boilerplate with domain-specific content (e.g., actual risk-per-trade percentages, a position-sizing formula, the Kelly criterion equation).

Fix the dangling reference: either ship `resources/implementation-playbook.md` or delete the pointer to it, and signal any remaining references with markdown links.

Add at least one validation checkpoint to the Approach sequence (e.g., verify that total portfolio heat from open positions stays under a stated risk budget).

DimensionReasoningScore

Conciseness

The Focus Areas, Approach, and Output sections are dense and earn their tokens, but the templated "Use this skill when / Do not use this skill when" and generic Instructions bullets ("Apply relevant best practices and validate outcomes") add no information Claude doesn't already have. Not 4 because that boilerplate padding is noticeable, not minor.

3 / 5

Actionability

Some genuinely concrete guidance exists — the expectancy formula "(Win% × Avg Win) - (Loss% × Avg Loss)" and the "1R = max loss" definition — but most steps are high-level directives ("Size positions based on account risk percentage", "Monitor correlations to avoid concentration") with no percentages, formulas, thresholds, or worked examples. Not 4 because key executable details (Kelly formula, sizing math, VaR method) are missing; not 2 because the formula and R-definition are directly usable.

3 / 5

Workflow Clarity

The Approach section lists a coherent 7-step sequence (define R → track → expectancy → size → monitor → hedge → document), but there are no validation checkpoints or feedback loops — "Apply relevant best practices and validate outcomes" is boilerplate, not a checkpoint. Not 4 because sequence is present but checkpoints are missing or only implicit.

3 / 5

Progressive Disclosure

Sections are well organized and the body is short, but the single external reference — "open `resources/implementation-playbook.md`" — points to a file that does not exist in the bundle (no resources/ directory), a dead-end navigation path. Not 4 because a clearly signaled but broken reference undermines the structure; not 2 because the inline content is short and appropriately placed.

3 / 5

Total

12

/

20

Passed

Description

66%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 compact, specific description with strong domain keywords and concrete actions. Its main defects are the missing "Use when..." trigger clause (capping completeness at 3) and coverage gaps for position sizing, VaR, and drawdown that leave some natural trigger terms absent.

Suggestions

Append an explicit trigger clause, e.g. "Use when the user asks about portfolio risk, trade risk, position sizing, drawdown, or hedging."

Mention position sizing, VaR, and maximum drawdown to round out capability coverage and capture more natural trigger terms.

Keep the third-person voice (already correct) while adding these terms without padding the description.

DimensionReasoningScore

Specificity

Lists several specific concrete actions — "Monitor portfolio risk, R-multiples, and position limits", "Creates hedging strategies", "calculates expectancy", "implements stop-losses" — each tied to the domain. Falls short of 5 because coverage has gaps: position sizing, VaR, correlation, and stress testing (all in the body's focus areas) are absent from the description.

4 / 5

Completeness

The "what" is clear and specific, but there is no "Use when..." clause or equivalent explicit trigger guidance — per the judging guidelines this caps completeness at 3. Not 4 because the "when" is entirely absent rather than merely implicit.

3 / 5

Trigger Term Quality

Good natural keyword coverage: "portfolio risk", "hedging", "stop-losses", "position limits", "R-multiples", "expectancy" — phrases a trader would actually say. Not 5 because common variations like "risk management", "position sizing", "VaR", and "drawdown" are missing.

4 / 5

Distinctiveness Conflict Risk

Terms like "R-multiples", "expectancy", and "hedging strategies" carve out a distinct trading-risk niche with clear triggers. Not 5 because "portfolio risk" alone could overlap with broader portfolio-management or general finance skills.

4 / 5

Total

15

/

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

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

plugins/AI-Agents-Safe-Coding-Skills/skills/risk-manager/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.