CtrlK
BlogDocsLog inGet started
Tessl Logo

position-sizer

Calculate risk-based position sizes for long stock trades. Use when user asks about position sizing, how many shares to buy, risk per trade, Kelly criterion, ATR-based sizing, fractional-share sizing, or portfolio risk allocation. Supports stop-loss distance calculation, volatility scaling, and sector concentration checks.

70

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

72%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, highly actionable skill body with executable CLI examples and one-level-deep references. The main weaknesses are inline time-sensitive regulatory dates that hurt conciseness and a workflow that lacks explicit validation checkpoints.

Suggestions

Move the FINRA intraday-margin date details (2026-06-04, phase-in through 2027-10-20) out of 'Key Principles' into a dedicated 'Regulatory notes' or deprecated/old-patterns section so time-sensitive facts don't bloat the main flow.

Add an explicit validation checkpoint to the workflow (e.g., Step 6: verify the generated JSON's final_recommended_shares against the binding constraint before presenting the recommendation to the user).

Trim Key Principles entries that restate well-known concepts (e.g., the 50%-loss/100%-gain asymmetry) to keep the body lean.

DimensionReasoningScore

Conciseness

Mostly efficient with organized sections, but time-sensitive FINRA dates (2026-06-04, phase-in through 2027-10-20) sit inline in 'Key Principles' rather than a deprecated/old-patterns section, and some principles restate concepts Claude already knows ('A 50% loss requires a 100% gain to recover').

2 / 3

Actionability

Multiple complete, copy-paste-ready bash invocations with real flags for all three modes, plus a full JSON output example and a real referenced script — fully executable guidance.

3 / 3

Workflow Clarity

A clear 6-step sequence is present, but there are no explicit validation or verification checkpoints (e.g., confirming the output JSON or reconciling the binding constraint), so checkpoints are missing/implicit rather than explicit.

2 / 3

Progressive Disclosure

SKILL.md is an overview that points one level deep to a real, substantive references/sizing_methodologies.md and scripts/position_sizer.py via a clearly signaled Resources section; content is appropriately split.

3 / 3

Total

10

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: third-person voice, concrete capabilities, and an explicit 'Use when' trigger clause with broad natural-language keywords. It clearly distinguishes the skill and answers both what it does and when to invoke it.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Calculate risk-based position sizes', 'stop-loss distance calculation, volatility scaling, and sector concentration checks' — rather than vague language.

3 / 3

Completeness

Explicitly answers both what ('Calculate risk-based position sizes for long stock trades') and when ('Use when user asks about...') with an explicit trigger clause.

3 / 3

Trigger Term Quality

'Use when user asks about position sizing, how many shares to buy, risk per trade, Kelly criterion, ATR-based sizing, fractional-share sizing, or portfolio risk allocation' covers natural terms a user would actually say.

3 / 3

Distinctiveness Conflict Risk

The long-stock risk-sizing niche with specialized triggers (Kelly criterion, ATR-based sizing, fractional-share sizing) is clearly distinct and unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
tradermonty/claude-trading-skills
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.