Skip to content
Development
Skill

/options-strategy

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

From plugin
claude-skills-collection
37137 skills

Claude Code

$ npx -y skills add nimadorostkar/Claude-Skills-collection --skill options-strategy --agent claude-code

SKILL.md

options-strategy.SKILL.md
name: options-strategy
description: 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.
metadata:
  category: finance
  version: 1.0.0
  tags: [options, greeks, volatility, spreads, risk]

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

1. **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. 2. **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. 3. **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. 4. **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. 5. **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. 6. **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_
Read more
@nimadorostkar
Ships withclaude-skills-collection

A curated library of 137 production-grade skills for Claude and other AI coding agents. Every skill follows one structure, speaks with one voice, and earns its place by changing what the agent does.

Stars on GitHub

Momentum

stars in total
37
Star history of nimadorostkar/Claude-Skills-collection on GitHub, a chart by star-history.com

Other skills on claude-skills-collection.

More skills from other plugins.

brainstorming
Auto-invoked

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…

@obra@obraInstall Skill
ask-matt

ask-matt

Ask which skill or flow fits your situation. A router over the skills in this repo.

skills2w309k
@mattpocock@mattpocockInstall Skill
accessibility
Auto-invoked

accessibility

Design, implement, and audit accessible UI to WCAG 2.2 Level AA across Web, iOS, and Android — semantic ARIA roles and labels,…

ecc2w293k
@affaan-m@affaan-mInstall Skill
compiler-commit

compiler-commit

Use when you want to verify compiler changes and commit with the correct convention. Runs tests, lint, and format, then commits…

react5d252k
@facebook@facebookInstall Skill

Questions about options-strategy.

Which coding agents can use options-strategy?
options-strategy installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.