Stockbee Momentum Burst Screener Skill for Muse
Screen US stocks for short-term breakout setups
- What
- Screen US stocks for short-term breakout setups
- Cost
- Free
- Needs
- Python 3 to run the bundled screening script; an FMP API key saved in the secure vault (a free tier exists at financialmodelingprep) for live universe scans, OR your own daily OHLCV price JSON if you prefer the no-API path. Fetch the whole skill folder: the SKILL.md, the scripts/ screening script, and the references/ methodology files.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Turns Muse into a disciplined stock screener for Stockbee-style short-term Momentum Burst setups: it runs a three-mode workflow (full universe scan, explicit symbols, or offline OHLCV JSON) detecting 4% breakouts, dollar breakouts, and range expansions, then scores each candidate on setup quality — trigger strength, volume expansion, base contraction, close location, risk distance to the trigger-day low — with failure filters and A/B/C ratings, handing survivors off to chart validation and position sizing. Discovered via skills.sh. Honest note: it is a candidate-generation workflow, not a signal service and not auto-execution — US equities only, and the scripted path needs Python plus an FMP API key (a free tier exists) or your own OHLCV data via the no-API path; screening candidates is research, not financial advice, and swing trading real money carries real risk. Skill Harbor never reviews the code, review it yourself before use. Not verified.
Curated by Skill Harbor — free, open-source skill (MIT) by @tradermonty.
Version:
Install
Prerequisites: Python 3 to run the bundled screening script; an FMP API key saved in the secure vault (a free tier exists at financialmodelingprep) for live universe scans, OR your own daily OHLCV price JSON if you prefer the no-API path. Fetch the whole skill folder: the SKILL.md, the scripts/ screening script, and the references/ methodology files. Install "Stockbee Momentum Burst Screener Skill for Muse" for me. Screens US equities for Stockbee-style short-term Momentum Burst setups: three input modes (universe scan, explicit symbols, offline OHLCV JSON), detection of 4% breakouts / dollar breakouts / range expansions, setup-quality scoring with failure filters and A/B/C ratings, and a conservative handoff to chart validation and position sizing. Repository: https://github.com/tradermonty/claude-trading-skills 1. Fetch the SKILL.md file (and its scripts/ and references/ folders) from the skill folder "stockbee-momentum-burst-screener" in the repository into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "stockbee-momentum-burst-screener". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. save my FMP API key in the vault, or prepare my OHLCV JSON, before the first screen). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.