scanner-pmcc
Skill411 starsChanged 8 days agoMITView on GitHub
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.
In this repository30 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- calendarSkill
- chart-ema-rsiSkill
- earnings-calendarSkill
- fundamentalsSkill
- greeksSkill
- ib-accountSkill
- ib-collarSkill
- ib-create-consolidated-reportSkill
- ib-find-short-rollSkill
- ib-option-chainSkill
- ib-pmcc-advisorSkill
- ib-portfolio-action-reportSkill
- ib-portfolioSkill
- ib-report-delta-adjusted-notional-exposureSkill
- ib-stop-lossSkill
- ib-trades-historySkill
- ib-trailing-stopSkill
- insider-tradingSkill
- markdown-to-pdfSkill
- news-sentimentSkill
- option-chainSkill
- price-historySkill
- report-stockSkill
- risk-assessmentSkill
- scanner-bullishSkill
- spread-analysisSkill
- stock-quoteSkill
- technical-analysisSkill
- whale-huntingSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 96
When the user asks for a report, a written analysis, or a saved document:
- Very specific: line 98
Run the scanner with --output to capture JSON data:
- Distinctive: line 103
Read the JSON output.
- Very specific: line 172
All timestamps and time-based calculations must use the America/New_York timezone.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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 365IV 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.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

