CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

parabolic-short-trade-planner

Screen US equities for parabolic exhaustion patterns and generate conditional pre-market short plans, then evaluate intraday trigger fires from live 5-min bars. Phase 1 daily 5-factor scorer (MA extension / acceleration / volume climax / range expansion / liquidity), Phase 2 per-candidate plans for ORL break / first-red 5-min / VWAP fail with explicit borrow / SSR / manual-confirmation gating, Phase 3 one-shot intraday FSM that detects trigger fires and resolves concrete share counts. Covers Phase 1 + Phase 2 + Phase 3.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

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

The body is a strong operational document: fully executable commands for all three phases, explicit prerequisites with documented fallbacks, idempotency and replay semantics, and a pre-entry review checklist. Weaknesses are modest — repeated safety disclaimers and time-sensitive regulatory dates hurt conciseness slightly, no explicit error-recovery loops in the workflow, and the large smoke-test runbook in the bundle is not surfaced in the Resources section.

Suggestions

Consolidate the no-order-routing safety statement into one authoritative location (e.g., the Overview or a dedicated Safety section) instead of repeating it in the Overview, "Do NOT invoke", and Phase 3 sections, and move the FINRA effective-date detail into references/short_risk_management.md.

Add references/smoke_test_runbook.md and the smoke_universe_*.csv fixtures to the Resources section so the bundle's testing artifacts are discoverable from the main file.

Add explicit error-recovery guidance for each phase (e.g., what to check when the FMP call fails, when output fails schema validation, or when Alpaca data is unavailable mid-session) to close the feedback-loop gap in workflow clarity.

DimensionReasoningScore

Conciseness

The body is dense and operational — full commands with flags, no explanations of concepts Claude already knows, and tight section structure. It is not a 5 because of minor trimmable material: the no-order-routing safety message is repeated three times (Overview, "Do NOT invoke", and the Phase 3 disclaimer), the FINRA date detail ("effective 2026-06-04, with broker phase-in allowed through 2027-10-20") is time-sensitive content outside a deprecated section, and legacy-compat notes ("earnings_within_2d is kept for backward compatibility") pad the earnings section. It is clearly above the 3 anchor since the bulk is efficient and every section carries operational weight.

4 / 5

Actionability

All three phases have copy-paste-ready commands with complete flags, input/output paths, and account parameters (e.g., "python3 skills/parabolic-short-trade-planner/scripts/screen_parabolic.py --mode safe_largecap --as-of 2026-04-30 --output-dir reports/"), plus env-var setup, fallback behavior without API keys, and fixture-based testing paths ("--dry-run --fixture <path>", "--bars-source fixture") that cover the common cases including API-less runs. Output file names and key fields are enumerated so the operator knows exactly what to inspect. This matches the 5 anchor; the only trivial nit (no literal `pip install -r requirements.txt` command) does not constitute a gap.

5 / 5

Workflow Clarity

The three-phase workflow is clearly sequenced with numbered steps, per-phase prerequisites (confirm FMP_API_KEY / ALPACA keys), documented fallbacks when prerequisites are missing, and an explicit pre-entry review checklist (plan_status / blocking_manual_reasons / advisory_manual_reasons). It falls short of the 5 anchor because there are no explicit validate→fix→retry feedback loops (e.g., what to do when a run fails or output fails schema validation is only implied via the referenced test suite), while it exceeds the 3 anchor because checkpoints are present and explicit at each phase, and the detection-only design means destructive-operation risk is absent by construction.

4 / 5

Progressive Disclosure

Good structure overall: the body keeps operational workflow inline and delegates domain depth to five clearly-signaled, one-level-deep reference files with one-line descriptions, and every referenced bundle path (references/*.md, scripts/tests/fixtures/dry_run_minimal.json, scripts/tests/fixtures/intraday_bars/, tests/test_schema_contract.py, tests/test_monitor_intraday_smoke.py) exists. It is not a 5 because the actual bundle contains discoverable content not navigable from SKILL.md — notably the 21KB references/smoke_test_runbook.md and the two smoke_universe_*.csv files are absent from the Resources section, leaving a substantial artifact undiscoverable.

4 / 5

Total

17

/

20

Passed

Description

75%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 highly specific and distinctive, with comprehensive concrete coverage of all three phases and strong domain keywords. Its main weakness is the missing explicit "Use when..." trigger guidance, which caps completeness, and the absence of natural synonyms (blow-off top, Qullamaggie, short watchlist) that users might actually say.

Suggestions

Add an explicit trigger clause such as "Use when the user wants a parabolic short / blow-off-top watchlist, pre-market short plans, or intraday short trigger monitoring for US equities" to answer 'when' and lift completeness.

Include natural synonyms users say in this niche — "parabolic short", "blow-off top", "Qullamaggie", "short watchlist" — to broaden trigger term coverage.

Drop the redundant closing sentence "Covers Phase 1 + Phase 2 + Phase 3" since the phases are already enumerated; use the space for the trigger clause.

DimensionReasoningScore

Specificity

The description lists multiple concrete, comprehensive actions across all three phases: "Screen US equities for parabolic exhaustion patterns", "generate conditional pre-market short plans", "evaluate intraday trigger fires from live 5-min bars", with named factors ("MA extension / acceleration / volume climax / range expansion / liquidity") and named triggers ("ORL break / first-red 5-min / VWAP fail"). This matches the 5 anchor (multiple specific concrete actions, comprehensive coverage); it is clearly above the 4 anchor because coverage of the skill's capabilities is essentially complete rather than having gaps.

5 / 5

Completeness

The "what" is clearly and thoroughly answered (screening, plan generation, intraday trigger evaluation with concrete mechanics), but there is no "Use when..." clause or equivalent explicit trigger guidance — "Covers Phase 1 + Phase 2 + Phase 3" describes scope, not invocation conditions. Per the judging guidelines, a missing explicit trigger clause caps completeness at 3; it cannot be 4 because the 'when' is not even weakly implied, and is above 2 because the 'what' is fully explicit.

3 / 5

Trigger Term Quality

Good domain keyword coverage: "parabolic exhaustion patterns", "pre-market short plans", "short", "intraday trigger fires", "5-min bars", "SSR", "VWAP fail", "borrow" — natural terms for the target trading audience. It falls short of the 5 anchor because common synonyms and phrasings users might say are absent (e.g., "blow-off top", "short watchlist", "Qullamaggie", "short screening"), while exceeding the 3 anchor since the included keywords are relevant and specific rather than partially covered.

4 / 5

Distinctiveness Conflict Risk

The description carves out a clear niche — US-equity parabolic short planning with borrow/SSR/manual-confirmation gating and intraday 5-min FSM monitoring — that would not plausibly trigger a different skill. It matches the 5 anchor (clear niche, distinct triggers, minimal conflict risk) and is above the 4 anchor because even closely related long-side screeners would not overlap with these triggers.

5 / 5

Total

17

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 2 deeper-than-1-level

Warning

Total

15

/

16

Passed

Repository

tradermonty/claude-trading-skills

Path

skills/parabolic-short-trade-planner/SKILL.md

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.