futures-position-sizer

Calculate contract-based futures position sizes from a direction, entry, and stop-loss, using verified per-symbol contract specs (multiplier, tick size, tick value). Use when the user asks how many futures contracts to trade, wants to size a futures position (ES, NQ, ZB, GC, CL, 6E/E6, VX, BT, ...), or is handing off a contrarian-setup-gate READY_FOR_PLAN direction/invalidation_level for sizing. Pure, offline calculation -- no API keys, no network.

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

85%

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 a clear multi-step workflow, validation checkpoints, and clean progressive disclosure to real bundle files. Its main weakness is verbosity in the Overview and Guardrails prose, which could be trimmed without losing clarity.

Suggestions

Trim the Overview's per-symbol dollar-value illustration ('$0.25 move is $12.50 on ES but $5.00 on NQ and $31.25 on ZB') and Guardrail 6's currency aside to tighten conciseness without losing the core point.

Condense Guardrail 2's exact-rational-arithmetic explanation to the essential claim (floor via Fraction, no epsilon) and move the full rationale pointer to references/sizing-methodology.md, which already covers it.

Consider moving the per-symbol contract-spec detail behind --list-specs into references/futures-contract-specs.md only, keeping the body focused on invocation and the output contract.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and filled with non-obvious domain detail (Fraction-based floor, 32nds notation, off-grid guards), but some prose could be tightened -- e.g. the Overview's multiplier-value illustration and Guardrails 2/6 explanatory asides -- so it leans verbose even though accurate.	2 / 3
Actionability	Fully executable, copy-paste-ready CLI commands for both modes, a WRONG-vs-CORRECT worked example, a --list-specs invocation, and a concrete YAML output-contract schema.	3 / 3
Workflow Clarity	Steps 1-4 are clearly sequenced with validation checkpoints (result-status table, warnings glossary, spec inspection) and the worked example demonstrates a reject-then-correct feedback loop for the bond off-grid guard.	3 / 3
Progressive Disclosure	A clear overview body with one-level-deep, well-signaled references -- each file in references/ and scripts/ is named in the Resources section with its purpose, and all referenced paths exist in the bundle.	3 / 3
	Total	11 / 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, third-person description that states concrete capabilities, gives natural user-facing triggers with a symbol list, and explicitly distinguishes itself from the sibling equity sizer. The only soft weakness is the pipeline-internal READY_FOR_PLAN trigger, which is jargon a lay user would not say.

Dimension	Reasoning	Score
Specificity	Names concrete actions -- 'Calculate contract-based futures position sizes from a direction, entry, and stop-loss, using verified per-symbol contract specs (multiplier, tick size, tick value)' -- listing multiple specific capabilities rather than vague language.	3 / 3
Completeness	Explicitly answers both 'what' (calculate contract-based futures position sizes) and 'when' via a 'Use when...' clause with multiple concrete triggers.	3 / 3
Trigger Term Quality	Covers natural phrasings users would say -- 'how many futures contracts to trade', 'size a futures position' -- plus a concrete symbol list (ES, NQ, ZB, GC, CL, 6E/E6, VX, BT, ...), though the pipeline-handoff trigger is more jargon-laden.	3 / 3
Distinctiveness Conflict Risk	A clear niche (futures contract sizing) with distinct triggers and explicit separation from the equity share-count position-sizer, making conflict unlikely.	3 / 3
	Total	12 / 12 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: tradermonty/claude-trading-skills
Path: skills/futures-position-sizer/SKILL.md
Commit: 62a1635

Reviewed: 5 days 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.