sizing

Position sizing with Kelly criterion and bankroll management

Quality

48%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./src/skills/bundled/sizing/SKILL.md

Quality

Content

64%

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 API reference for Kelly criterion position sizing with strong actionability through concrete TypeScript examples and chat commands. However, it's somewhat verbose with redundant examples and formula explanations Claude doesn't need, and it lacks workflow guidance showing how to sequence decisions (calculate edge → check threshold → size position → validate exposure). The content would benefit from being split into a concise overview SKILL.md and a detailed API reference file.

Suggestions

Add a workflow section showing the decision sequence: calculate edge → check minimum edge threshold → choose Kelly fraction → validate against position limits → execute, with explicit validation checkpoints

Move the detailed API reference (multi-outcome Kelly, portfolio Kelly, confidence-adjusted, etc.) to a separate REFERENCE.md and keep SKILL.md as a concise overview with quick-start examples

Remove the Formulas section — Claude already knows the Kelly criterion formula — or reduce it to a single-line reminder

Dimension	Reasoning	Score
Conciseness	The content is reasonably efficient but includes some redundancy — the fractional Kelly examples repeat similar patterns multiple times, and the formulas section explains basic Kelly math that Claude already knows. The chat commands section and API reference could be tighter.	2 / 3
Actionability	The skill provides fully executable TypeScript code examples with concrete parameters, clear API signatures, and copy-paste ready snippets. Chat commands are shown with specific argument patterns and examples.	3 / 3
Workflow Clarity	The skill presents individual API calls clearly but lacks a coherent workflow sequence — there's no guidance on when to use which sizing method, no validation steps (e.g., checking if edge is sufficient before sizing), and no error handling or feedback loops for when positions exceed limits.	2 / 3
Progressive Disclosure	The content is a monolithic reference document at ~200 lines that could benefit from splitting the detailed API reference into a separate file. The structure within the file is decent with clear sections, but everything is inline with no references to supplementary materials.	2 / 3
	Total	9 / 12 Passed

Description

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 specific niche (Kelly criterion-based position sizing) but reads more like a topic label than a functional skill description. It lacks concrete actions, explicit trigger guidance ('Use when...'), and sufficient keyword coverage to reliably distinguish it from related finance or betting skills.

Suggestions

Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user asks about optimal bet sizing, Kelly criterion calculations, bankroll management, or risk-of-ruin analysis.'

List specific concrete actions the skill performs, e.g., 'Calculates optimal position sizes using the Kelly criterion, estimates risk of ruin, and models bankroll growth under various edge and variance scenarios.'

Include natural keyword variations users might say, such as 'bet sizing', 'stake sizing', 'money management', 'optimal allocation', 'edge-based betting', and 'risk of ruin'.

Dimension	Reasoning	Score
Specificity	Names the domain (position sizing, bankroll management) and a specific method (Kelly criterion), but doesn't list concrete actions like 'calculate optimal bet size', 'simulate drawdown scenarios', or 'compute edge-based allocations'.	2 / 3
Completeness	Describes a rough 'what' but has no 'when' clause or explicit trigger guidance. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and the 'what' itself is also weak, so this scores a 1.	1 / 3
Trigger Term Quality	Includes some relevant keywords ('Kelly criterion', 'position sizing', 'bankroll management') that users might naturally say, but misses common variations like 'bet sizing', 'risk of ruin', 'stake sizing', 'money management', or 'optimal allocation'.	2 / 3
Distinctiveness Conflict Risk	'Kelly criterion' is fairly distinctive and unlikely to conflict with many other skills, but 'position sizing' and 'bankroll management' could overlap with general finance, trading, or gambling skills without clearer scoping.	2 / 3
	Total	7 / 12 Passed

Validation

90%

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 — 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: e71a5f6

Reviewed: 2 months ago

Table of Contents

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.