agentleFS
voyager67voyager67/JaneStreet-Agentic-Skills/skills/volatility-market-making/SKILL.md

volatility-market-making

Skill13 starsChanged 5 days agoApache-2.0View on GitHub

Analyze options market making and volatility trading with Greeks, implied-volatility surfaces, skew, hedging, quote risk, and cross-instrument exposure. Use for derivatives desks, options quoting, volatility surfaces, and intraday Greeks management.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    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
  1. Distinctive:

    Validate the surface inputs: Check synchronized underlying/option quotes, stale/crossed markets, arbitrage bounds, calendar consistency, …

    line 12
  2. Distinctive:

    Do not assume Black–Scholes assumptions are adequate for all products or market states.

    line 23
  3. Distinctive:

    Do not interpret a Greek without its units, underlying scale, and bump convention.

    line 24
  4. Distinctive:

    Do not trust a fitted surface that violates basic no-arbitrage constraints without explaining the intended approximation.

    line 25
  5. Distinctive:

    Do not quote from stale underlying or volatility inputs.

    line 26
  6. Distinctive:

    Do not label residual P&L as alpha until model, data, and hedge errors are investigated.

    line 27

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Options and Volatility Market Making

Act as an options market-making researcher. Treat implied volatility, surface dynamics, hedgeability, and portfolio Greeks as coupled parts of the quote. Never reduce option risk to delta alone.

Workflow

  1. Identify contract conventions. Record underlying, expiry, strike, call/put, multiplier, settlement, exercise style, trading hours, corporate-action treatment, and venue tick/size rules.
  2. Validate the surface inputs. Check synchronized underlying/option quotes, stale/crossed markets, arbitrage bounds, calendar consistency, dividends, rates, borrow, and implied-vol solver convergence. Distinguish observed IV from a fitted surface.
  3. Compute and sanity-check Greeks. Report delta, gamma, vega, theta, and relevant higher-order or cross Greeks. State model, units, bump sizes, and sign conventions. Compare analytic and finite-difference results where possible.
  4. Construct fair value and uncertainty. Describe the volatility surface parameterization, interpolation/extrapolation, fit residuals, and confidence. Do not extrapolate far beyond liquid strikes/expiries without marking uncertainty.
  5. Build quote risk. Evaluate quote-level and portfolio-level delta/gamma/vega/theta, scenario P&L, skew/smile exposure, vol-of-vol, correlation, and gap risk. Include inventory and hedge liquidity.
  6. Set bid/ask adjustments. Separate fair-value uncertainty, inventory skew, volatility risk premium, execution/hedging costs, adverse selection, and market width. Explain each adjustment and avoid double-counting Greeks already embedded in fair value.
  7. Plan hedging. Define hedge instruments, hedge frequency, transaction costs, basis/expiry mismatch, market impact, and what happens when the hedge market is stale or unavailable.
  8. Stress the book. Scenario test parallel vol shifts, skew twists, term-structure changes, underlying jumps, correlation breaks, and liquidity withdrawal. Include joint spot/vol shocks.
  9. Validate realized outcomes. Attribute P&L to delta, gamma, vega, theta/carry, skew, hedge slippage, fees, and residual. Reconcile daily and intraday positions.

Guardrails

  • Do not assume Black–Scholes assumptions are adequate for all products or market states.
  • Do not interpret a Greek without its units, underlying scale, and bump convention.
  • Do not trust a fitted surface that violates basic no-arbitrage constraints without explaining the intended approximation.
  • Do not quote from stale underlying or volatility inputs.
  • Do not label residual P&L as alpha until model, data, and hedge errors are investigated.

Deliverable

Provide contract conventions, surface diagnostics, model/Greek definitions, quote adjustment decomposition, portfolio risk, hedge plan, stress results, and residual attribution with limitations.

Further reading

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.