
scanner-pmcc
Scan stocks for Poor Man's Covered Call (PMCC) suitability. Analyzes LEAPS and short call options for delta, liquidity, spread, IV, yield, trend direction, and earnings proximity. Use when user asks about PMCC candidates, diagonal spreads, or LEAPS strategies.
- Installs
- 86
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/staskh/trading_skills --skill scanner-pmcc- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads scanner-pmcc automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
PMCC Scanner
Finds optimal Poor Man's Covered Call setups by scoring symbols on option chain quality.
What is PMCC?
Buy deep ITM LEAPS call (delta ~0.80) + Sell short-term OTM call (delta ~0.20) against it. Cheaper alternative to covered calls.
Instructions
Note: If
uvis not installed orpyproject.tomlis not found, replaceuv run pythonwithpythonin all commands below.
uv run python scripts/scan.py SYMBOLS [options]
Arguments
SYMBOLS- Comma-separated tickers or path to JSON file from bullish scanner--min-leaps-days- Minimum LEAPS expiration in days (default: 270 = 9 months)--leaps-delta- Target LEAPS delta (default: 0.80)--short-delta- Target short call delta (default: 0.20)--output- Save results to JSON file (use this; Claude generates the report from the JSON)--report- Save auto-generated markdown to file (programmatic fallback only — prefer Claude-generated reports)
Scoring System (max possible: 14, range: -8 to 14)
| Category | Condition | Points |
|---|---|---|
| Delta Accuracy | LEAPS within ±0.05 | +2 |
| LEAPS within ±0.10 | +1 | |
| Short within ±0.05 | +1 | |
| Short within ±0.10 | +0.5 | |
| Liquidity | LEAPS vol+OI > 100 | +1 |
| LEAPS vol+OI > 20 | +0.5 | |
| Short vol+OI > 500 | +1 | |
| Short vol+OI > 100 | +0.5 | |
| Spread | LEAPS spread < 5% | +1 |
| LEAPS spread < 10% | +0.5 | |
| Short spread < 10% | +1 | |
| Short spread < 20% | +0.5 | |
| IV Level | 25-50% (ideal) | +2 |
| 20-60% | +1 | |
| Yield | Annual > 50% | +2 |
| Annual > 30% | +1 | |
| Annual > 15% | +0.5 | |
| Trend | Price > SMA50 | +1 / -1 |
| RSI > 50 | +0.5 / -0.5 | |
| MACD > signal | +0.5 / -0.5 | |
| Earnings | Next earnings > 45 days | +1.0 |
| Earnings within 45 days | -1.0 | |
| Earnings within short expiry | -2.0 | |
| Weekly Options | No weekly options listed | -1 |
| Strike Density | < 3 strikes spot→short | -2 |
| < 5 strikes spot→short | -1 | |
| Short Premium | Short mid < $0.10 | -1 |
| Short mid < $0.50 | -0.5 |
Weekly-options, strike-density, and short-premium are penalty-only (0 at best), so
max_possible_score stays 14 while the theoretical minimum is -8 (base 0,
trend -2, earnings -2, weekly -1, strike -2, short premium -1).
Output
Returns JSON with:
criteria- Scan parameters usedresults- Array sorted by score:symbol,price,iv_pct,pmcc_score,max_possible_score(always 14)industry- GICS industry (falls back to sector), or nulldescription- one-sentence company description, or nullhas_weeklies- whether the symbol lists weekly options (bool)short_window- short-expiry window actually used:"7-21"or"5-30 (fallback)"dividend_yield- continuous dividend yield (fraction) used in the BS/IV mathleaps- expiry, strike, delta, iv (calculated from bid/ask), last_price, bid/ask, spread%, volume, OIshort- expiry, strike, delta, iv (calculated from bid/ask), last_price, bid/ask, spread%, volume, OIearnings_date- next earnings date (YYYY-MM-DD) or nullmetrics- net_debit, short_yield% (period yield over the short window), annual_yield%, capital_requiredscore_breakdown- every scoring component as a<name>_delta(float) +<name>(explanation string) pair:- Base:
leaps_delta,short_delta,leaps_liquidity,short_liquidity,leaps_spread,short_spread,iv,yield - Trend:
trend_delta,trend(per-indicator dict) - Earnings:
earnings_delta,earnings - Weekly options:
weekly_options_delta,weekly_options - Strike density:
strike_density_delta,strike_density - Short premium:
short_premium_delta,short_premium - All
_deltavalues sum topmcc_score
- Base:
errors- Symbols that failed (no options, insufficient data)
Report Generation
When the user asks for a report, a written analysis, or a saved document:
-
Run the scanner with
--outputto capture JSON data:uv run python scripts/scan.py SYMBOLS --output sandbox/PMCC_Scan_YYYY-MM-DD_HHmm.json -
Read the JSON output.
-
Generate the markdown report yourself using the template defined in
templates/markdown-template.md. Do not use the--reportflag — that produces mechanical string output. Claude-generated reports include real analysis, contextual warnings, and trader-relevant narrative. -
Save the generated markdown to
sandbox/PMCC_Scan_YYYY-MM-DD_HHmm.md(match the JSON timestamp). -
Display the full report to the user.
Examples
# Scan specific symbols
uv run python scripts/scan.py AAPL,MSFT,GOOGL,NVDA
# Scan and save JSON for report generation
uv run python scripts/scan.py AAPL,MSFT,GOOGL --output sandbox/PMCC_Scan_2026-01-15_1430.json
# Use output from bullish scanner
uv run python scripts/scan.py bullish_results.json
# Custom delta targets
uv run python scripts/scan.py AAPL,MSFT --leaps-delta 0.70 --short-delta 0.15
# Longer LEAPS (1 year minimum)
uv run python scripts/scan.py AAPL,MSFT --min-leaps-days 365
IV Calculation
IV is always computed from market price data via Black-Scholes, never taken from Yahoo Finance's impliedVolatility column:
- During trading hours: IV derived from bid/ask mid price
- Off-hours (bid=ask=0): IV derived from last price, using the option's last trade timestamp as the pricing moment (not current wall-clock time)
This applies to both compute_atm_iv (used for scanner baseline IV) and per-option delta calculations.
Dividends: the Black-Scholes inversion uses the underlying's continuous dividend
yield (Merton model). Ignoring it biases recovered IV downward for calls on dividend
payers — badly for high yielders (e.g. a 7%-yield name would read ~12% IV instead of
~24%). The yield is normalized from yfinance's inconsistent fields (dividendRate/price,
then trailingAnnualDividendYield, then dividendYield) and reported as dividend_yield
(a fraction) in each result. The same yield feeds the strike-selection deltas and the
max-profit repricing.
Key Constraints
- Short strike must be above LEAPS strike
- Options with bid = 0 and no last price are skipped
- Moderate IV (25-50%) scores highest
Interpretation
- Score > 12: Excellent candidate (strong structure + bullish trend + clear earnings runway)
- Score 10-12: Good candidate
- Score 6-10: Acceptable with caveats
- Score < 6: Poor structure, bearish trend, or earnings risk
max_possible_scoreis always 14 — usepmcc_score / max_possible_scoreto gauge how close a candidate is to perfect- Off-hours scores are not comparable to market-hours scores. When bid/ask aren't both > 0 (outside trading hours),
spread_pctis forced to 100%, which zeroes out both spread scores (−2 vs a live scan). A candidate can look up to 2 points worse simply because it was scanned off-hours. Compare candidates only within the same scan.
Dependencies
numpypandasscipyyfinance
Timezone
All timestamps and time-based calculations must use the America/New_York timezone. All JSON output must include generated_at (NY time string) and data_delay fields.
FAQ
What does the scanner-pmcc skill do?
Scan stocks for Poor Man's Covered Call (PMCC) suitability. Analyzes LEAPS and short call options for delta, liquidity, spread, IV, yield, trend direction, and earnings proximity. Use when user asks about PMCC candidates, diagonal spreads, or LEAPS strategies.
How do I install scanner-pmcc?
Run npx skills add https://github.com/staskh/trading_skills --skill scanner-pmcc in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/scanner-pmcc/ (personal) or .claude/skills/scanner-pmcc/ (project).
Which AI agents can use scanner-pmcc?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is scanner-pmcc safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains scanner-pmcc?
It is published by staskh in staskh/trading_skills. It has 86 recorded installs.
More from staskh/trading_skills
technical-analysis
staskh/trading_skills
Compute technical indicators like RSI, MACD, Bollinger Bands, SMA, EMA for a stock. Use when user asks about technical analysis, indicators, RSI, MACD, moving averages, overbought/oversold, or chart analysis.
news-sentiment
staskh/trading_skills
Open the skill to read its SKILL.md instructions.
fundamentals
staskh/trading_skills
Open the skill to read its SKILL.md instructions.
stock-quote
staskh/trading_skills
Open the skill to read its SKILL.md instructions.
greeks
staskh/trading_skills
Open the skill to read its SKILL.md instructions.
report-stock
staskh/trading_skills
Open the skill to read its SKILL.md instructions.
Popular business & finance skills
sales-enablement
coreyhaines31/marketingskills
When the user wants to create sales collateral, pitch decks, one-pagers, objection handling docs, or demo scripts. Also use when the user mentions 'sales deck,' 'pitch deck,' 'one-pager,' 'leave-behind,' 'objection handling,' 'deal-specific ROI analysis,' 'demo script,' 'talk track,' 'sales playbook,' 'proposal template,' 'buyer persona card,' 'battle card,' 'battlecard,' 'competitive one-pager,' 'win-loss analysis,' 'why are we losing deals,' 'loss reasons,' 'how do I respond to this objection,' 'prospect just said,' 'help my sales team,' 'sales materials,' or 'what should I give my sales reps,' 'cold call script,' or 'voicemail script.' Use this for any document or asset that helps a sales team close deals. For public competitor comparison pages, see competitors. For running buyer interviews or churn research, see customer-research. For marketing website copy, see copywriting. For cold outreach emails, see cold-email. For the offer being sold (bonuses, guarantees, pricing structure),
revops
coreyhaines31/marketingskills
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,' 'outbound pipeline stages,' '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 emails. For pricing decisions, see pricing.
sales-funnel-blueprint
autonnel/autonnel-skills
Turn an offer into a concrete multi-step sales funnel spec - page-by-page structure, price ladder, copy outline and the metrics each step must hit. Use when asked to build a sales funnel, marketing funnel, landing page flow, lead magnet funnel, webinar funnel, tripwire or VSL funnel, when planning a product launch page flow, or when someone asks "what pages do I need" for selling something online.
pricing
coreyhaines31/marketingskills
When the user wants help with pricing decisions, packaging, or monetization strategy. Also use when the user mentions 'pricing,' 'pricing tiers,' 'freemium,' 'free trial,' 'packaging,' 'price increase,' 'value metric,' 'Van Westendorp,' 'willingness to pay,' 'monetization,' 'how much should I charge,' 'my pricing is wrong,' 'pricing page,' 'annual vs monthly,' 'per seat pricing,' 'should I offer a free plan,' 'pricing page teardown,' 'pricing page audit,' 'is my pricing page AI-readable,' or 'can AI read my pricing.' Use this whenever someone is figuring out what to charge, how to structure their plans, or wants to audit a pricing page (for humans and for the AI agents that shortlist tools). For in-app upgrade screens, see paywalls. For offer construction (bonuses, guarantees, value framing, naming) on services/courses/coaching/high-ticket B2B, see offers.
cross-border-ecommerce
nexscope-ai/ecommerce-skills
Cross-border e-commerce expansion advisor. Scores target markets on 8 weighted dimensions (market size, ecommerce penetration, competition, regulatory complexity, logistics infrastructure, payment ecosystem, cultural distance, IP protection), compares 5 fulfillment models with cost and transit data, provides country-by-country tax/duty compliance guides (EU VAT/IOSS, UK VAT, US sales tax, CA GST, AU GST, JP consumption tax), maps local payment preferences by market, and builds a phased expansion roadmap. No API key required.
pricing-strategy
coreyhaines31/marketingskills
When the user wants help with pricing decisions, packaging, or monetization strategy. Also use when the user mentions 'pricing,' 'pricing tiers,' 'freemium,' 'free trial,' 'packaging,' 'price increase,' 'value metric,' 'Van Westendorp,' 'willingness to pay,' 'monetization,' 'how much should I charge,' 'my pricing is wrong,' 'pricing page,' 'annual vs monthly,' 'per seat pricing,' or 'should I offer a free plan.' Use this whenever someone is figuring out what to charge or how to structure their plans. For in-app upgrade screens, see paywall-upgrade-cro.