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.

72

Quality

91%

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

78%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.

A strong, highly actionable skill body: executable commands for every mode, a clear six-step workflow, and correct use of one-level-deep bundle references. The main weaknesses are redundancy around fractional-share mode and dated regulatory text inline, which cost token efficiency without adding proportionate guidance.

Suggestions

Collapse the five near-duplicate bash blocks into one canonical invocation plus a short table of mode-specific flags, and consolidate the fractional-share guidance (currently in Overview, Step 1, Step 2, and Key Principles) into a single place.

Move the dated FINRA intraday-margin detail (effective 2026-06-04, phase-in through 2027-10-20) into references/sizing_methodologies.md and keep only a short 'check your broker's current intraday margin rules' pointer in the body.

Add a brief validation checkpoint after running the script (e.g., confirm the output JSON's final_risk_pct is within the requested risk budget and re-check inputs on error) to close the workflow's feedback-loop gap.

DimensionReasoningScore

Conciseness

The body is mostly efficient and skill-specific, but it repeats the fractional-share guidance in at least four places (Overview, Step 1, a full extra bash example, Key Principles 3-4) and the five near-duplicate bash blocks could be collapsed into one command plus a flag table. It also embeds time-sensitive regulatory detail with specific dates ("effective 2026-06-04, with broker phase-in allowed through 2027-10-20") outside any 'old patterns' section, which the guidelines penalize. Not score 4 because these are more than minor trimmable instances; not score 2 because there is no padding that explains concepts Claude already knows.

3 / 5

Actionability

Every workflow step is backed by copy-paste-ready commands: five complete bash invocations covering fixed-fractional, fractional, ATR, and both Kelly modes, plus a constraints example and a concrete JSON output schema. The examples cover the common cases exactly as the top anchor requires. Not score 4 because the commands are complete and executable as written with all flags and realistic values.

5 / 5

Workflow Clarity

The six steps are clearly sequenced with concrete commands and explicit decision points (mode selection in Step 1, scenario comparison in Step 4, binding-constraint explanation in Step 5). This is a read-only calculation skill, so the destructive/batch cap does not apply. Not score 5 because there are no explicit validation checkpoints or error-recovery loops (e.g., what to do if the script errors or inputs are inconsistent); not score 3 because the sequence itself is complete and checkpoints are only implicit, not missing.

4 / 5

Progressive Disclosure

The body is a workflow-focused overview that delegates methodology depth to a well-signaled, one-level-deep reference ("Read `references/sizing_methodologies.md`", listed again in Resources with a description), and the calculation logic to `scripts/position_sizer.py`; both files exist in the bundle. Not score 4 because there is no inline content that clearly belongs in a separate file and all references are clearly signaled in both the workflow and a Resources section.

5 / 5

Total

17

/

20

Passed

Description

100%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 a model example: a concrete capability statement in third person, followed by an explicit 'Use when' clause covering both colloquial and technical trigger phrases, plus named sub-capabilities. It is concise, specific, and highly distinguishable from neighboring finance skills.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "Calculate risk-based position sizes", "stop-loss distance calculation, volatility scaling, and sector concentration checks" — matching the comprehensive-coverage anchor. Not score 4 because there are no meaningful coverage gaps: the three sizing methods and their supporting calculations are all named.

5 / 5

Completeness

Both parts are explicit: the "what" is stated up front ("Calculate risk-based position sizes for long stock trades") and the "when" is a concrete "Use when user asks about..." clause with specific trigger phrases. Not score 4 because the when-clause is already fully explicit, not merely implied or general.

5 / 5

Trigger Term Quality

"position sizing, how many shares to buy, risk per trade, Kelly criterion, ATR-based sizing, fractional-share sizing, or portfolio risk allocation" comprehensively covers the natural phrases a user would say, including technique names and colloquial variants. Not score 4 because no common synonym or variation is obviously missing.

5 / 5

Distinctiveness Conflict Risk

It carves out a clear niche (risk-based position sizing for long stock trades) with distinct triggers like Kelly criterion and ATR-based sizing that are unlikely to fire for a generic portfolio or stock-screening skill. Not score 4 because overlap risk with closely related skills is minimal given the precise scope statement.

5 / 5

Total

20

/

20

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.

Validation — 16 / 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.