Tessl • The management layer for AI agent skills

Blog Docs Log inGet started

SkillPublic

sizing

Position sizing with Kelly criterion and bankroll management

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

82%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 strong, executable API reference with copy-paste TypeScript and CLI examples and useful reference tables, with only minor conciseness and organization gaps. It would benefit from a short top-of-file quick-start and optionally splitting the full API reference into a referenced file.

Suggestions

Lead with a concise quick-start snippet (one Kelly calculation) before the full API reference so the most common case is reachable without scrolling.

Consider moving the complete TypeScript API reference into a referenced file (e.g. references/API.md) and keeping SKILL.md as a tight overview, improving progressive disclosure.

Trim the small redundancies between inline code comments and the Kelly-fractions table to tighten conciseness.

Dimension	Reasoning	Score
Conciseness	The body is an efficient API reference of executable TypeScript and CLI blocks with tables and only light redundancy (e.g. the Kelly-fractions table restates in-comment guidance), fitting the 'efficient; minor instances of over-explanation that could be trimmed' anchor rather than the perfectly lean 5.	4 / 5
Actionability	Copy-paste-ready TypeScript examples (createSizingCalculator, kelly, kellyMultiOutcome, kellyPortfolio) and concrete chat commands cover the common cases with shown outputs, matching the 'fully executable; copy-paste ready' anchor.	5 / 5
Workflow Clarity	Operations are read-only calculations with no destructive/batch steps, so the destructive-cap does not apply; sections are clearly delineated and each action is unambiguous, but there is no explicit multi-step sequence or checkpoint, placing it at 'clear sequence with most checkpoints' (4) rather than a full sequenced-workflow 5.	4 / 5
Progressive Disclosure	No bundle files exist (references/, scripts/, assets/ absent) and the content is a single well-sectioned reference file with clear headers, fitting 'good structure; most content appropriately placed; minor organization gaps'; it is not the lean overview-pointing-to-references 5 because everything is inlined in one ~240-line file.	4 / 5
	Total	17 / 20 Passed

Description

48%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 names a precise, distinctive niche but provides no concrete actions and, critically, no 'Use when' trigger guidance, capping completeness at 3. Adding explicit trigger phrases and a couple of concrete verbs would lift specificity and completeness.

Suggestions

Add a 'Use when...' clause stating when Claude should invoke this skill (e.g. 'Use when sizing trades, managing bankroll, or calculating Kelly-optimal stakes').

Replace the passive 'with' framing with concrete action verbs such as 'Calculate', 'Allocate', and 'Estimate' to surface specific capabilities.

Include natural user phrasings and synonyms like 'bet sizing', 'stake sizing', or 'risk per trade' to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Quotes 'Position sizing with Kelly criterion and bankroll management' name the domain but use no concrete action verbs ('calculate', 'allocate', 'size') beyond the domain nouns themselves, matching the 'names the domain but actions are minimal' anchor rather than the 3-anchor which requires 1-2 concrete actions.	2 / 5
Completeness	It gives a clear 'what' (position sizing with Kelly and bankroll management) but has no 'Use when...' clause or equivalent trigger guidance, so per the boundary guidance completeness is capped at 3.	3 / 5
Trigger Term Quality	'Kelly criterion', 'position sizing', and 'bankroll' are relevant domain keywords a knowledgeable user would say, but common variations and synonyms (e.g. 'bet sizing', 'stake', 'risk per trade') are missing, fitting the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	The Kelly-criterion/bankroll niche is mostly distinct with only minor overlap risk against generic finance or risk-management skills, matching the 'mostly distinct; minor overlap risk' anchor rather than the fully-conflict-free 5 anchor which wants explicit trigger phrases.	4 / 5
	Total	12 / 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/sizing/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.

sizing

Table of Contents

Is this your skill?