options-strategy
Skill37 starsChanged 37 days agoMITView on GitHub
Use when analyzing or constructing an options position. Covers the greeks in practical terms, implied volatility and its term structure, common structures and their true risk, and assignment and expiration mechanics. Trigger on "should i sell puts or buy calls here", "is iv too high to buy this option", "what happens if my short call gets assigned". Do not use for deciding how much capital to commit — see the position-sizing skill.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- PatrickSUDO/fadacai-portfoliotheir own version, first seen Nov 13, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- PatrickSUDO/fadacai-portfolio★ 145same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository137 other files it gives its agents.
- agent-instructionsSkill
- agent-memorySkill
- hooksSkill
- plugin-developmentSkill
- skill-authoringSkill
- skill-reviewSkill
- slash-commandsSkill
- subagentsSkill
- agent-designSkill
- context-engineeringSkill
- fine-tuningSkill
- llm-cost-optimizationSkill
- llm-evaluationSkill
- llm-integrationSkill
- mcp-serverSkill
- ml-pipelineSkill
- model-selectionSkill
- prompt-engineeringSkill
- ragSkill
- structured-outputSkill
- api-designSkill
- background-jobsSkill
- cachingSkill
- djangoSkill
- event-driven-architectureSkill
- fastapiSkill
- graphqlSkill
- microservicesSkill
- nestjsSkill
- realtime-websocketsSkill
- spring-bootSkill
- competitive-analysisSkill
- lead-researchSkill
- product-analysisSkill
- resumeSkill
- user-researchSkill
- database-performanceSkill
- data-modelingSkill
- data-qualitySkill
- pandasSkill
- postgresSkill
- sparkSkill
- brand-guidelinesSkill
- generative-artSkill
- themingSkill
- ui-reviewSkill
- visual-designSkill
- architecture-decisionsSkill
- bug-fix-protocolSkill
- cli-developmentSkill
- code-reviewSkill
- debuggingSkill
- design-patternsSkill
- domain-modelingSkill
- git-workflowSkill
- legacy-modernizationSkill
- refactoringSkill
- repository-explorationSkill
- simple-designSkill
- system-designSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 57
Never sell a naked call. The loss is unbounded and the premium collected is finite.
≈ “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
Options Strategy
Purpose
Construct and analyze options positions with an accurate view of what is actually being risked. Options positions frequently have a risk profile very different from the one the buyer had in mind, and the difference shows up at expiration.
When to Use
- Constructing an options position to express a view.
- Analyzing the risk of an existing position.
- Deciding whether implied volatility makes an option cheap or expensive.
- Managing a position into expiration or assignment.
Capabilities
- The greeks: delta, gamma, theta, vega — and what each one actually costs you.
- Implied volatility, IV rank, and term structure.
- Structures: spreads, straddles, strangles, calendars, and their real risk profiles.
- Assignment, exercise, and pin risk.
- Position management and adjustment.
Inputs
- The view: direction, magnitude, and time frame. All three are required.
- Current implied volatility, and where it sits historically.
- Liquidity of the specific contracts, not just the underlying.
Outputs
- A structure that matches the view.
- Maximum loss, maximum gain, and breakeven — computed, not assumed.
- The conditions under which the position is exited.
Workflow
- State the view precisely — Direction, magnitude, and time frame. An option requires all three. "I think it goes up" is not sufficient to choose a structure; being right about direction and wrong about timing loses money.
- Check where implied volatility sits — Buying options when IV is at the 90th percentile of its own history means you need a large move just to overcome the volatility crush. Selling when IV is at the 10th percentile means being paid very little for real risk.
- Choose the structure that matches — Long options for a large, fast move with defined risk. Spreads to reduce cost and cap gain. Selling premium only when IV is elevated and the risk is genuinely defined.
- Compute the actual maximum loss — Not the one you imagine. For a naked short option, it is unbounded, and that is not a figure of speech.
- Plan the exit before entry — Including what happens at expiration. Positions held into expiration have assignment and pin risk that did not exist the day before.
- Check the liquidity of the contracts — A liquid underlying can have illiquid options. A wide bid-ask spread is a cost you pay twice.
Best Practices
- Theta is not free money. Selling premium collects small amounts consistently and loses large amounts occasionally. The strategy's profit and loss distribution is not the same shape as its win rate, and a 90% win rate can still be a losing strategy.
- Gamma is what kills short-option positions. A short option that is comfortably out of the money is safe until the underlying approaches the strike, at which point the delta changes rapidly and the loss accelerates.
- Buying options into an earnings announcement means buying elevated IV that collapses the moment the announcement occurs. You can be right about the direction and still lose money — this is the most common options mistake there is.
- Never sell a naked call. The loss is unbounded and the premium collected is finite. There is no position size at which this is a good trade.
- Long options lose money every day the underlying does not move. Time decay accelerates in the final month.
- An option position with no exit plan will be held to expiration, which is a decision, and usually the wrong one.
Examples
The IV crush that catches everyone:
Situation: earnings in 2 days. You expect a large move.
Stock at $100. The 30-day at-the-money straddle costs $8.00.
Implied volatility: 68% (its 52-week range is 24%-71%).
The market has priced a ±8% move. For the long straddle to profit, the stock
must move MORE than 8%.
After the announcement, IV collapses to ~30% regardless of the direction of
the move — the uncertainty that justified 68% has been resolved.
Outcome if the stock moves 6% (a large move, and you were directionally right):
Intrinsic value gained : ~$6.00
Value lost to IV crush : ~$7.20 (vega ~0.18 x 38 vol points)
Net : approximately -$1.20 per share. A loss.
You predicted the direction, the stock moved substantially, and you lost money.
This is the standard outcome of buying options into earnings and it surprises
people every quarter.
The structure that expresses "large move" without paying for elevated IV is a
calendar or a diagonal — long the far-dated option (less vega-sensitive to the
front-month crush), short the front. Or simply take a stock position.Computing the real risk, not the imagined one:
def position_risk(legs: list[OptionLeg], underlying: float) -> RiskProfile:
prices = np.linspace(underlying * 0.5, underlying * 1.5, 400)
pnl = np.array([sum(leg.payoff_at_expiry(p) for leg in legs) for p in prices])
has_naked_short_call = any(
leg.is_short and leg.is_call and not _is_covered(leg, legs) for leg in legs
)
return RiskProfile(
max_gain=float(pnl.max()),
# This is the number people get wrong.
max_loss=float("-inf") if has_naked_short_call else float(pnl.min()),
breakevens=[float(p) for p in _zero_crossings(prices, pnl)],
net_debit=sum(leg.cost for leg in legs),
# Aggregate greeks: the position's actual exposure, not each leg's.
net_delta=sum(leg.delta * leg.quantity * 100 for leg in legs),
net_theta=sum(leg.theta * leg.quantity * 100 for leg in legs),
net_vega=sum(leg.vega * leg.quantity * 100 for leg in legs),
warning=(
"UNBOUNDED LOSS: this position contains a naked short call. There is "
"no maximum loss. Do not size this as if there were."
if has_naked_short_call else None
),
)Notes
- The earnings IV-crush example is the single most valuable thing in this skill. Being right about the direction and losing money is deeply counterintuitive, and it happens to nearly every options trader once.
- A 90% win rate on short premium is compatible with losing money overall: nine wins of $100 and one loss of $2,000 is a losing strategy with an excellent win rate. Look at expectancy, never at the win rate alone.
- This is educational material about options mechanics, not financial advice. Options can lose their entire value, and short options can lose more than the account holds.
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.

