sizing
Position sizing with Kelly criterion and bankroll management
Overall
score
61%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
33%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 lacks concrete actions and explicit trigger guidance. It reads more like a topic label than a functional skill description, missing the 'when to use' clause that would help Claude select it appropriately from a large skill library.
Suggestions
Add a 'Use when...' clause with trigger terms like 'calculate bet size', 'optimal position', 'Kelly formula', 'risk of ruin', or 'bankroll allocation'
List specific concrete actions such as 'Calculate optimal position sizes using Kelly criterion, determine risk-adjusted bet amounts, compute expected value and edge'
Include common user phrasings and variations like 'how much should I bet', 'optimal stake size', 'money management for trading/betting'
| 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', 'determine risk allocation', or 'compute expected value'. | 2 / 3 |
Completeness | Only addresses 'what' at a high level with no 'Use when...' clause or explicit trigger guidance. Missing when Claude should select this skill over others. | 1 / 3 |
Trigger Term Quality | Includes relevant terms like 'position sizing', 'Kelly criterion', and 'bankroll management' that users familiar with trading/betting would use, but misses common variations like 'bet sizing', 'risk management', 'optimal stake', 'portfolio allocation', or 'money management'. | 2 / 3 |
Distinctiveness Conflict Risk | 'Kelly criterion' is fairly distinctive and technical, but 'position sizing' and 'bankroll management' could overlap with general trading, investing, or gambling skills without clearer boundaries. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
65%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid API reference skill with excellent actionability - the code examples are concrete, executable, and cover multiple use cases from basic to portfolio-level Kelly. However, it's somewhat verbose for Claude (explaining formulas Claude knows) and could benefit from better progressive disclosure by splitting the detailed API reference into a separate file while keeping SKILL.md as a quick-start overview.
Suggestions
Remove the Formulas section - Claude already knows Kelly criterion mathematics
Split the detailed TypeScript API Reference into a separate REFERENCE.md file, keeping only quick-start examples in SKILL.md
Add validation guidance for edge cases (e.g., what to do when Kelly returns negative values, how to verify edge estimates)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with good code examples, but includes some unnecessary elements like the formulas section (Claude knows Kelly formula) and the explanatory table headers. The best practices section is useful but could be more concise. | 2 / 3 |
Actionability | Excellent executable code examples throughout - TypeScript API calls are copy-paste ready with realistic parameters, chat commands are concrete with clear syntax, and output examples show expected results. | 3 / 3 |
Workflow Clarity | This is primarily a reference/API skill rather than a multi-step workflow, but the best practices section hints at a process without explicit validation steps. No guidance on verifying calculations or handling edge cases like negative Kelly values. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections (Chat Commands, TypeScript API, Formulas, Best Practices), but everything is in one monolithic file. The API reference section could be split out, and there are no references to external files for advanced topics like correlation matrices. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
91%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 | |
- 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.