CtrlK
BlogDocsLog inGet started
Tessl Logo

risk-manager

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

45

Quality

47%

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

Quality

Content

28%Scale 1-5

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

This skill reads as a high-level topic outline rather than actionable guidance. It lists many risk management concepts (VaR, Kelly criterion, R-multiples, hedging) but provides no concrete implementations, formulas, code, or executable examples for any of them. The output section is a wish list of deliverables without templates or examples showing what they should look like.

Suggestions

Add executable code examples for core calculations: Kelly criterion formula, VaR calculation, R-multiple tracking, and expectancy computation with sample data.

Replace the generic 'Output' bullet list with concrete templates or example outputs (e.g., a sample risk dashboard in markdown, a position sizing calculation with specific numbers).

Add validation checkpoints to the workflow, such as verifying position sizes don't exceed account limits, checking correlation matrix validity, and confirming stop-loss levels are within acceptable ranges.

Remove boilerplate sections ('Use this skill when' / 'Do not use this skill when') and generic instructions ('Clarify goals, constraints, and required inputs') that waste tokens without adding actionable guidance.

DimensionReasoningScore

Conciseness

The skill contains significant padding: generic 'Use this skill when' / 'Do not use this skill when' sections that add no value, vague boilerplate instructions ('Clarify goals, constraints, and required inputs'), and a long bullet list of outputs that are merely labels without substance. It explains concepts Claude already knows at a surface level without adding novel information.

2 / 5

Actionability

The content is almost entirely abstract and descriptive. There are no concrete code examples, no executable commands, no formulas beyond a single inline expectancy formula, and no specific implementation details. The 'Approach' section lists high-level steps but lacks the specifics needed to actually execute any of them (e.g., no Kelly criterion formula, no VaR calculation code, no example of R-multiple tracking).

2 / 5

Workflow Clarity

The 'Approach' section provides a rough sequence of 7 steps, but they are high-level descriptions without validation checkpoints, error handling, or feedback loops. For a skill involving financial risk calculations (which are consequential), there are no verification steps to confirm calculations are correct, no bounds checking, and no explicit validation of outputs.

2 / 5

Progressive Disclosure

There is a reference to 'resources/implementation-playbook.md' for detailed examples, which suggests some progressive disclosure intent. However, no bundle files exist to support this reference, the reference is vaguely signaled ('If detailed examples are required'), and the bulk of the content that should be in supporting files (like formulas, code examples, templates) is neither inline nor properly referenced elsewhere.

3 / 5

Total

9

/

20

Passed

Description

66%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.

The description does a good job listing specific trading risk management capabilities with domain-appropriate terminology. Its main weakness is the absence of an explicit 'Use when...' clause, which limits completeness and could make skill selection less reliable. Adding trigger guidance and a few more synonym terms would strengthen it significantly.

Suggestions

Add a 'Use when...' clause with trigger phrases like 'Use when the user asks about portfolio risk management, position sizing, stop-loss placement, trade expectancy, or hedging.'

Include additional natural synonyms such as 'risk management', 'position sizing', 'drawdown', and 'risk-reward ratio' to improve trigger term coverage.

DimensionReasoningScore

Specificity

Lists several specific actions: monitor portfolio risk, R-multiples, position limits, create hedging strategies, calculate expectancy, implement stop-losses. Good coverage of concrete actions, though some could be more detailed (e.g., what types of hedging strategies).

4 / 5

Completeness

The 'what' is clearly stated with multiple concrete capabilities. However, there is no explicit 'when' clause (no 'Use when...' or equivalent trigger guidance), which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

Includes strong domain-specific trigger terms like 'portfolio risk', 'R-multiples', 'position limits', 'hedging strategies', 'expectancy', and 'stop-losses'. These are natural terms a user in trading/investing would use. Missing some synonyms like 'risk management', 'position sizing', 'drawdown', or 'risk-reward ratio'.

4 / 5

Distinctiveness Conflict Risk

The combination of portfolio risk management, R-multiples, expectancy, and stop-losses creates a fairly distinct niche in trading risk management. Minor overlap risk with general portfolio management or trading skills, but the specific risk-focused terminology makes it mostly distinguishable.

4 / 5

Total

15

/

20

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

10

/

11

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-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.