risk
Unified risk engine with VaR, stress testing, volatility regimes, and automated controls
68
56%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./src/skills/bundled/risk/SKILL.mdQuality
Discovery
32%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 identifies a clear financial risk management domain with some specific technical capabilities, but fails to provide any trigger guidance for when Claude should use this skill. The feature-list style lacks action verbs describing concrete behaviors, and the absence of a 'Use when...' clause significantly limits its utility for skill selection.
Suggestions
Add an explicit 'Use when...' clause with trigger scenarios like 'Use when calculating portfolio risk, running stress tests, analyzing market volatility, or setting risk limits'
Convert feature list to action verbs: 'Calculates Value at Risk (VaR), runs stress tests, detects volatility regime changes, and enforces automated risk controls'
Include common user phrasings and variations: 'risk management', 'portfolio risk', 'market risk', 'risk metrics', 'risk analysis'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (risk) and lists some specific capabilities (VaR, stress testing, volatility regimes, automated controls), but these are listed as features rather than concrete actions. Missing verbs describing what it actually does with these capabilities. | 2 / 3 |
Completeness | Describes what capabilities exist but provides no 'Use when...' clause or any guidance on when Claude should select this skill. The 'when' component is completely absent. | 1 / 3 |
Trigger Term Quality | Includes relevant technical terms like 'VaR', 'stress testing', 'volatility regimes' that finance users would recognize, but missing common variations like 'Value at Risk', 'risk management', 'portfolio risk', or 'market risk' that users might naturally say. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of VaR, stress testing, and volatility regimes is fairly specific to quantitative finance risk management, but 'risk' and 'automated controls' are generic enough to potentially overlap with other risk-related skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
79%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a comprehensive, well-structured API reference with excellent actionability and conciseness. The code examples are executable and the tables provide quick reference for configurations. However, the document is quite long and could benefit from splitting advanced topics into separate files, and the recovery/reset workflows lack explicit validation checkpoints for these potentially risky operations.
Suggestions
Add explicit validation steps to the Recovery Process section (e.g., 'Verify positions are closed before reset', 'Check dashboard shows safe state before resuming')
Split advanced topics (stress testing customization, circuit breaker configuration, VaR calculator details) into separate reference files linked from the main skill
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, presenting commands, code examples, and tables without unnecessary explanation. It assumes Claude understands TypeScript, trading concepts, and API patterns without over-explaining. | 3 / 3 |
Actionability | Provides fully executable TypeScript code examples with proper imports, concrete chat commands, and copy-paste ready snippets. Every section includes specific, runnable examples rather than abstract descriptions. | 3 / 3 |
Workflow Clarity | The 10-step validation sequence is clearly documented in a table, but the recovery process lacks explicit validation checkpoints. For risky operations like kill switch recovery, there's no feedback loop or verification step before resuming trading. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections and tables, but it's a monolithic 200+ line document. Advanced topics like stress testing customization and circuit breaker configuration could be split into separate reference files with links from the main skill. | 2 / 3 |
Total | 10 / 12 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.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- alsk1992/CloddsBot
- Commit
2a8c94e
- 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.