breakout-trade-planner

Generate Minervini-style breakout trade plans from VCP screener output with worst-case risk calculation, portfolio heat management, and Alpaca-compatible order templates (stop-limit bracket for pre-placement, limit bracket for post-confirmation). Use when user has VCP screener results and wants actionable trade plans with entry/stop/target levels and position sizing.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Quality

Content

72%

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

The content is highly actionable and well-structured with appropriate one-level-deep references, but loses points on conciseness due to an inline regulatory/date paragraph and on workflow clarity due to missing validation checkpoints for a batch order-generation operation.

Suggestions

Move the FINRA intraday-margin regulatory detail (effective 2026-06-04, phase-in through 2027-10-20) into a separate 'Regulatory notes' or 'old patterns' reference file, keeping Step 3 focused on what to confirm with the user.

Add an explicit validation checkpoint before presenting orders, e.g. verify the input schema_version is 1.0 and confirm portfolio heat/risk limits are not exceeded, with a fix-and-retry loop for failures.

Tighten Step 3 by replacing the dense regulatory sentence with a concise instruction to confirm the user's broker intraday/day-trading controls when the plan could create same-day round trips or use margin.

Dimension	Reasoning	Score
Conciseness	The body is largely lean (tables, a copy-paste command, no basic-concept padding), but the inline time-sensitive FINRA intraday-margin paragraph with specific dates (2026-06-04, 2027-10-20) is not placed in a deprecated/old-patterns section, which per the guidelines warrants tightening.	2 / 3
Actionability	Provides a fully executable bash command with concrete arguments, a complete CLI parameter table with defaults, and concrete output filenames — copy-paste ready matching the score-3 anchor.	3 / 3
Workflow Clarity	Three steps are clearly sequenced, but for a batch order-generation operation with portfolio-risk and broker constraints there is no validation/verification checkpoint or validate->fix->retry loop, which caps workflow clarity at 2 per the rubric feedback-loops note.	2 / 3
Progressive Disclosure	Well-organized overview with sections, and a single clearly signaled one-level-deep reference (references/minervini_entry_rules.md, confirmed present) plus the real scripts bundle referenced via the CLI path.	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.

The description is specific, complete, and distinctive, naming concrete capabilities and providing an explicit use-trigger clause with natural terminology. It is a strong, concise description with no padding.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions (generate trade plans, worst-case risk calculation, portfolio heat management, Alpaca-compatible order templates with stop-limit/limit bracket variants, position sizing) matching the score-3 anchor.	3 / 3
Completeness	Clearly answers both what (generate trade plans with risk calc, heat management, order templates) and when via an explicit 'Use when...' clause, matching the score-3 anchor.	3 / 3
Trigger Term Quality	Trigger clause uses terms a user of this workflow would naturally say ('VCP screener results', 'breakout entry/stop/target levels', 'position sizing'), giving good coverage of natural phrasings.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear niche (VCP screener -> Minervini breakout plans -> Alpaca order templates) with distinctive triggers unlikely to conflict with other skills.	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/breakout-trade-planner/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.