Tessl • The management layer for AI agent skills

Blog Docs Log inGet started

SkillPublic

risk

Unified risk engine with VaR, stress testing, volatility regimes, and automated controls

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./src/skills/bundled/risk/SKILL.md

Quality

Content

72%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 content is highly actionable with executable code and commands throughout, but it is a monolithic API reference that should be split into referenced files, and its destructive/batch workflows (kill switch, circuit breaker) lack validation checkpoints. Structure is present but progressive disclosure and workflow validation are the weak points.

Suggestions

Move the bulk TypeScript API reference into a separate file (e.g., references/API.md) and keep only a quick-start example in SKILL.md, linking out for the rest.

Add explicit validation/feedback steps to destructive workflows — e.g., after '/risk kill', instruct to confirm positions are flat and that '/risk reset' requires manual review before re-arming.

Remove the duplicated Risk Engine Checks table (it restates the numbered list above it) to tighten token use.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient reference material with executable code blocks and minimal concept-explanation padding, though the duplicated Risk Engine Checks table and several long API reference sections could be trimmed into a separate file for tighter token use.	4 / 5
Actionability	Provides copy-paste-ready TypeScript snippets and concrete chat commands for every capability (validateTrade, recordPnL, getPortfolioRisk, stress tests, circuit breaker), covering the common cases with executable, complete code.	5 / 5
Workflow Clarity	Multi-step risky operations (trip/reset breaker, kill switch, recording P&L that feeds VaR) are sequenced as commands but lack explicit validation checkpoints or feedback loops, and the destructive/batch guideline caps destructive-operation workflows at 3.	3 / 5
Progressive Disclosure	There is clear section structure with headers and tables, but the entire API reference (200+ lines of code that clearly belong in a separate file) is inlined and there are no bundle files to offload it to; references are not signaled because none exist.	3 / 5
	Total	15 / 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.

The description is specific and distinct, naming concrete risk-engine capabilities, but it lacks an explicit 'Use when...' trigger clause, which limits its completeness and weakens activation guidance. It reads as a capable feature summary rather than a trigger-oriented skill description.

Suggestions

Add an explicit 'Use when...' clause naming natural trigger phrases (e.g., 'Use when managing trading risk, setting loss limits, running stress tests, or checking VaR').

Lead with concrete action verbs ('Validates trades, computes VaR, runs stress tests, detects volatility regimes') to strengthen the 'what'.

Include common synonyms or shorthand a user might say (e.g., 'risk limits', 'kill switch', 'circuit breaker') to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Lists several concrete capabilities — 'VaR', 'stress testing', 'volatility regimes', 'automated controls' — naming the domain and multiple specific actions, but lacks explicit action verbs (extract/generate/validate) and has minor coverage gaps (e.g., circuit breakers and kill switches appear only in the body, not the description).	4 / 5
Completeness	It has a clear 'what' (a unified risk engine with named capabilities) but no 'when/Use when...' clause or equivalent trigger guidance, which per the guidelines caps completeness at 3.	3 / 5
Trigger Term Quality	Includes strong natural risk-management terms users would say ('risk', 'VaR', 'stress testing', 'volatility') but is missing a few common synonyms and lacks explicit file/flag-style triggers; good but not comprehensive coverage.	4 / 5
Distinctiveness Conflict Risk	The 'unified risk engine' niche with VaR and volatility regimes is fairly distinct and unlikely to trigger for unrelated skills, with only minor overlap risk against generic finance/trading skills.	4 / 5
	Total	15 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: alsk1992/CloddsBot
Path: src/skills/bundled/risk/SKILL.md
Revision: c930628

Reviewed: 1 month ago

Discovery Implementation Validation

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.

risk

Table of Contents

Is this your skill?