Parabolic Short Trade Planner logo

Parabolic Short Trade Planner

CommunityPopular
tradermonty
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.

Overview

Publishertradermonty
Repositoryclaude-trading-skills
Skill nameparabolic-short-trade-planner
Stars
2.8K
Forks
647
Bundled files
86
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 86 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by tradermonty on GitHub. Read the source before you install it.

Installation

Install the Parabolic Short Trade Planner AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/tradermonty/claude-trading-skills.git /tmp/claude-trading-skills
mkdir -p .claude/skills
cp -r /tmp/claude-trading-skills/skills/parabolic-short-trade-planner .claude/skills/parabolic-short-trade-planner
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Parabolic Short Trade Planner in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Parabolic Short Trade Planner on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Parabolic Short Trade Planner is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Overview

Generate Qullamaggie-style Parabolic Short watchlists and conditional pre-market plans for US equities. The skill never sends orders. It emits JSON + Markdown that a human reviews against their broker before entry.

Three phases:

  • Phase 1 (screen_parabolic.py): pulls EOD bars + company profile from FMP, applies hard invalidation rules (mode-aware), scores survivors on 5 factors (weights 30/25/20/15/10), and assigns A/B/C/D grades.
  • Phase 2 (generate_pre_market_plan.py): takes the Phase 1 JSON, filters by --tradable-min-grade (default B), checks Alpaca short inventory (or ManualBrokerAdapter), evaluates SEC Rule 201 SSR state from the inherited prior-day close, and renders three trigger plans per candidate.
  • Phase 3 (monitor_intraday_trigger.py): reads the Phase 2 plan, fetches 5-min bars (Alpaca live or fixture), walks each plan's FSM forward by one step, persists per-plan state, and writes an intraday_monitor JSON with state, entry_actual, stop_actual, and shares_actual (when triggered). One-shot — trader runs it every 1–5 min via watch or cron; replay-deterministic so re-runs are byte-identical.

When to Use

Invoke this skill when the user wants to:

  • Build a daily Parabolic Short watchlist from S&P 500 (or a custom CSV).
  • Translate a watchlist into pre-market trade plans with explicit borrow / SSR / state-cap gating.
  • Audit a candidate's blocking vs advisory manual-confirmation reasons before placing an order at Alpaca.

Do NOT invoke for:

  • Long-side momentum screening — use vcp-screener or canslim-screener.
  • 1-minute / sub-minute intraday signals — Phase 3 evaluates 5-min bars only.
  • Live order routing — this skill is detection-only by design; Phase 3 emits a triggered state with concrete entry/stop/share count, but the trader fires the order manually.

Workflow

Phase 1 — daily screener

  1. Confirm FMP_API_KEY is set (env var or --api-key).
  2. Run with the safer-by-default mode:
    bash
    python3 skills/parabolic-short-trade-planner/scripts/screen_parabolic.py \
      --mode safe_largecap --as-of 2026-04-30 --output-dir reports/
  3. Inspect reports/parabolic_short_<date>.md — the watchlist is grouped by grade (A→D).
  4. Promote interesting names to Phase 2.

For small-cap blow-offs, switch to --mode classic_qm (looser market cap and ADV floors, higher 5-day ROC threshold).

For testing without the API, run --dry-run --fixture <path> against a JSON fixture (one is shipped at scripts/tests/fixtures/dry_run_minimal.json).

Phase 2 — pre-market plan generator

  1. Optional: set ALPACA_API_KEY / ALPACA_SECRET_KEY for live borrow checks. Without them the planner falls back to ManualBrokerAdapter, which marks every candidate as borrow_inventory_unavailable / plan_status: watch_only.
  2. Run:
    bash
    python3 skills/parabolic-short-trade-planner/scripts/generate_pre_market_plan.py \
      --candidates-json reports/parabolic_short_2026-04-30.json \
      --account-size 100000 --risk-bps 50 --output-dir reports/
  3. Output: reports/parabolic_short_plan_<date>.json. Each plan contains three entry plans (5min ORL break, first red 5-min, VWAP fail) with entry_hint / stop_hint formula strings (no baked-in shares — the trader computes shares at trigger time from the shares_formula).

Phase 3 — intraday trigger monitor

  1. Confirm ALPACA_API_KEY / ALPACA_SECRET_KEY are set (Phase 3 uses Alpaca market data; data.alpaca.markets works for both paper and live accounts).
  2. During US regular session, run one-shot per cadence — typical is every 60 s during the first 30 min, then every 5 min:
    bash
    python3 skills/parabolic-short-trade-planner/scripts/monitor_intraday_trigger.py \
      --plans-json reports/parabolic_short_plan_2026-05-05.json \
      --bars-source alpaca \
      --state-dir state/parabolic_short/ \
      --output-dir reports/
    Or wrap in watch -n 60 'python3 ...' / cron.
  3. Output: reports/parabolic_short_intraday_<date>.json lists every monitored plan with state (armed / triggered / invalidated / FSM-specific), bar-derived transition timestamps, and size_recipe_resolved (concrete shares_actual) when triggered.
  4. For testing without the API, use --bars-source fixture --bars-fixture <path> against a JSON fixture (scripts/tests/fixtures/intraday_bars/).

Phase 3 trigger detection is not an order instruction. Before any manual short entry, confirm borrow/locate availability, SEC Rule 201 SSR state, broker short-sale controls, and the broker's current intraday margin or day-trading controls. FINRA replaced the old pattern-day-trader day-count and $25,000 minimum-equity requirements with intraday margin standards effective 2026-06-04, with broker phase-in allowed through 2027-10-20.

Phase 3 is idempotent: each run replays the full session bars from open up to now_et (or --now-et override), so re-running during the same minute produces the same state. prior_state is used only for diff/notification display; it never advances the FSM.

Reviewing a plan before entry

Read three top-level fields per ticker:

  • plan_status: actionable (manual gates can be cleared) or watch_only (hard blockers — borrow unavailable or SSR active).
  • blocking_manual_reasons: must all be resolved before pulling the trigger.
  • advisory_manual_reasons: heads-up only, e.g. manual_locate_required (always set), warning:too_early_to_short, warning:recent_earnings_catalyst (last earnings within --earnings-catalyst-window-days, default 10 trading days — flag the move as event-driven rather than pure technical blow-off).

Earnings-aware screening

Phase 1 fetches the FMP earnings calendar once per run (single call, not per-symbol) and emits two earnings-aware checks:

  • --exclude-earnings-within-days (default 2 calendar days, forward) — hard invalidation when next earnings is within the window. Matches the legacy earnings_blackout_days semantic.
  • --earnings-catalyst-window-days (default 10 trading days, backward) — soft warning recent_earnings_catalyst when last earnings is within the window. Routes to Phase 2 as an advisory manual reason without forcing trade_allowed_without_manual: false.

Per-candidate output exposes last_earnings_date, next_earnings_date, trading_days_since_earnings (TRADING days), earnings_within_days (CALENDAR days, forward), earnings_blackout_days (configured threshold), and earnings_in_blackout_window. The legacy earnings_within_2d is kept for backward compatibility.

Top-level dates: as_of is the planning date (Phase 2 contract — never mutate); run_date mirrors it; market_data_as_of is the latest bar date used for technical metrics (differs from as_of on weekend runs).

Exchange Calendar and Replay

Install requirements.txt before running the planner. Phase 1 --as-of uses strict YYYY-MM-DD, filters bars beyond that ceiling, and counts earnings age with XNYS sessions. Phase 3 uses actual holidays and early closes; the close boundary is exclusive. Historical dates are accepted only with Phase 1 --dry-run fixture data; live universe and profile endpoints are not PIT and therefore fail closed for a non-current --as-of.

Output Format

Phase 1 JSON: parabolic_short_<as_of>.json (schema_version 1.0). Phase 2 JSON: parabolic_short_plan_<as_of>.json (schema_version 1.0). Phase 3 JSON: parabolic_short_intraday_<as_of>.json (schema_version 1.0, phase = intraday_monitor). The contract is pinned by tests/test_schema_contract.py plus tests/test_monitor_intraday_smoke.py for Phase 3.

Resources

  • references/parabolic_short_methodology.md — Qullamaggie's 3-trigger framework and exhaustion signals.
  • references/short_invalidation_rules.md — mode-aware exclusion rules.
  • references/short_risk_management.md — Rule 201, ETB vs HTB, locate.
  • references/intraday_trigger_playbook.md — detail on each trigger type, the FSM transitions Phase 3 implements, and same-bar tie-break semantics.
  • references/broker_capability_matrix.md — what each broker exposes through its API for short inventory.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

and 26 more files.

Frequently asked questions

What does the Parabolic Short Trade Planner AI skill do?

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.

Why use Parabolic Short Trade Planner on TypingMind?

Because you install it once and use it with any model. Parabolic Short Trade Planner is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Parabolic Short Trade Planner in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/tradermonty/claude-trading-skills/tree/main/skills/parabolic-short-trade-planner. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Parabolic Short Trade Planner?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Parabolic Short Trade Planner?

As many as you like. As long as a model supports skills, you can use Parabolic Short Trade Planner with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Parabolic Short Trade Planner AI skill free?

Yes. It is published on GitHub by tradermonty under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇