skills/pead-screener/SKILL.md
Screen post-earnings gap-up stocks for PEAD (Post-Earnings Announcement Drift) patterns. Analyzes weekly candle formation to detect red candle pullbacks and breakout signals. Supports two input modes - FMP earnings calendar (Mode A) or earnings-trade-analyzer JSON output (Mode B). Use when user asks about PEAD screening, post-earnings drift, earnings gap follow-through, red candle breakout patterns, or weekly earnings momentum setups.
npx skillsauth add MileniumTick/skills pead-screenerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Screen post-earnings gap-up stocks for PEAD (Post-Earnings Announcement Drift) patterns using weekly candle analysis to detect red candle pullbacks and breakout signals.
FMP_API_KEY environment variable or pass --api-key)
export FMP_API_KEY=your_api_key_here
Run the PEAD screener script in one of two modes:
Mode A (FMP earnings calendar):
# Default: last 14 days of earnings, 5-week monitoring window
python3 skills/pead-screener/scripts/screen_pead.py --output-dir reports/
# Custom parameters
python3 skills/pead-screener/scripts/screen_pead.py \
--lookback-days 21 \
--watch-weeks 6 \
--min-gap 5.0 \
--min-market-cap 1000000000 \
--output-dir reports/
Mode B (earnings-trade-analyzer JSON input):
# From earnings-trade-analyzer output
python3 skills/pead-screener/scripts/screen_pead.py \
--candidates-json reports/earnings_trade_analyzer_YYYY-MM-DD_HHMMSS.json \
--min-grade B \
--output-dir reports/
references/pead_strategy.md for PEAD theory and pattern contextreferences/entry_exit_rules.md for trade management rulesFor each candidate, present:
Based on stages and ratings:
pead_screener_YYYY-MM-DD_HHMMSS.json - Structured results with stage classificationpead_screener_YYYY-MM-DD_HHMMSS.md - Human-readable report grouped by stagereferences/pead_strategy.md - PEAD theory and weekly candle approachreferences/entry_exit_rules.md - Entry, exit, and position sizing rulesdevelopment
Writes, reviews, and debugs idiomatic Rust code with memory safety and zero-cost abstractions. Implements ownership patterns, manages lifetimes, designs trait hierarchies, builds async applications with tokio, and structures error handling with Result/Option. Use when building Rust applications, solving ownership or borrowing issues, designing trait-based APIs, implementing async/await concurrency, creating FFI bindings, or optimizing for performance and memory safety. Invoke for Rust, Cargo, ownership, borrowing, lifetimes, async Rust, tokio, zero-cost abstractions, memory safety, systems programming.
development
Guide for writing idiomatic Rust code based on Apollo GraphQL's best practices handbook. Use this skill when: (1) writing new Rust code or functions, (2) reviewing or refactoring existing Rust code, (3) deciding between borrowing vs cloning or ownership patterns, (4) implementing error handling with Result types, (5) optimizing Rust code for performance, (6) writing tests or documentation for Rust projects.
development
Master Rust async programming with Tokio, async traits, error handling, and concurrent patterns. Use when building async Rust applications, implementing concurrent systems, or debugging async code.
tools
When the user wants help with revenue operations, lead lifecycle management, or marketing-to-sales handoff processes. Also use when the user mentions 'RevOps,' 'revenue operations,' 'lead scoring,' 'lead routing,' 'MQL,' 'SQL,' 'pipeline stages,' 'deal desk,' 'CRM automation,' 'marketing-to-sales handoff,' 'data hygiene,' 'leads aren't getting to sales,' 'pipeline management,' 'lead qualification,' or 'when should marketing hand off to sales.' Use this for anything involving the systems and processes that connect marketing to revenue. For cold outreach emails, see cold-email. For email drip campaigns, see email-sequence. For pricing decisions, see pricing-strategy.