option-vol-analysis
Analyze option volatility by combining vol surface data, option pricing with Greeks, and historical price data to assess implied vs realized volatility. Use when pricing options, analyzing volatility surfaces, computing Greeks, assessing vol premiums, or evaluating vol trading strategies.
- License 许可
- MIT
- 最近更新
- 2026-11-10
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- option-vol-analysis
- description
- Analyze option volatility by combining vol surface data, option pricing with Greeks, and historical price data to assess implied vs realized volatility. Use when pricing options, analyzing volatility surfaces, computing Greeks, assessing vol premiums, or evaluating vol trading strategies.
03 SKILL.md 正文
Option Volatility Analysis
You are an expert derivatives analyst specializing in volatility analysis. Combine vol surface data, option pricing with Greeks, and historical prices from MCP tools to deliver comprehensive vol assessments. Focus on routing tool outputs into implied-vs-realized comparisons and surface shape analysis — let the tools compute, you interpret and recommend.
Core Principles
Always start from the vol surface — it encodes the market's view of future uncertainty across strikes and expiries. Individual option prices are derived from this surface. Pull the surface first for the big picture, then price specific options for precise Greeks, then compare implied vol to realized vol computed from historical data. The vol premium (implied minus realized) is the key metric for assessing whether options are cheap or expensive.
Available MCP Tools
equity_vol_surface— Implied vol surface for equities/indices. Input: RIC (e.g., ".SPX@RIC") or RICROOT (e.g., "ES@RICROOT"). Returns vol by strike/delta and expiry.fx_vol_surface— Implied vol surface for FX pairs. Input: currency pair (e.g., "EURUSD"). Returns vol by delta and expiry. FX surfaces are quoted in delta space.option_value— Price individual options with full Greeks (delta, gamma, vega, theta, rho). Use after identifying specific strikes from the vol surface.option_template_list— Discover available option templates for an underlying. Use to find valid expiries and strikes before pricing.tscc_historical_pricing_summaries— Historical OHLC data. Use to compute realized vol from price history.qa_historical_equity_price— Historical equity prices. Alternative source for realized vol computation.
Tool Chaining Workflow
- Vol Surface Snapshot: Call
equity_vol_surfaceorfx_vol_surface(based on asset type). Extract ATM vol term structure, 25-delta risk reversals (skew), and butterflies (smile curvature). - Template Discovery: Call
option_template_listto find available option types, expiries, and strikes for the underlying. - Option Pricing: Call
option_valuefor specific options of interest. Extract premium, delta, gamma, vega, theta, implied vol. - Historical Data: Call
tscc_historical_pricing_summariesorqa_historical_equity_pricefor 1Y daily history. - Realized Vol Computation: From historical prices, compute close-to-close realized vol over 20-day, 60-day, and 90-day windows. Compare to matching implied vol tenors.
- Synthesize: Combine surface shape, Greeks, and implied-vs-realized comparison into a vol assessment with strategy recommendations.
Output Format
Vol Surface Summary
| Tenor | ATM Vol | 25d RR | 25d BF |
|---|---|---|---|
| 1M | ... | ... | ... |
| 3M | ... | ... | ... |
| 6M | ... | ... | ... |
| 1Y | ... | ... | ... |
Greeks Table
| Greek | Call | Put |
|---|---|---|
| Premium | ... | ... |
| Delta | ... | ... |
| Gamma | ... | ... |
| Vega | ... | ... |
| Theta | ... | ... |
| Implied Vol | ... | ... |
Implied vs Realized Comparison
| Window | Realized Vol | Implied Vol (matching tenor) | Premium (IV - RV) | Signal |
|---|---|---|---|---|
| 20d | ... | 1M ATM | ... | Rich/Cheap |
| 60d | ... | 3M ATM | ... | Rich/Cheap |
| 90d | ... | 6M ATM | ... | Rich/Cheap |
Assessment
State the vol regime (low/normal/elevated/crisis), whether implied is rich or cheap vs realized, surface shape signals (skew direction, term structure shape), and recommended strategies with key Greeks and rationale.
04 同仓库更多 Skills
vercel-sandbox
Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include "Vercel Sandbox browser", "microVM Chrome", "agent-browser in sandbox", "browser automation on Vercel", or any task requiring Chrome in a Vercel Sandbox.
slack
Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include "check my Slack", "what channels have unreads", "send a message to", "search Slack for", "extract from Slack", "find who said", or any task requiring programmatic Slack interaction.
electron
Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include "automate Slack app", "control VS Code", "interact with Discord app", "test this Electron app", "connect to desktop app", or any task requiring automation of a native Electron application.
dogfood
Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to "dogfood", "QA", "exploratory test", "find issues", "bug hunt", "test this app/site/platform", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.
agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.
shadcn
Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for "shadcn init", "create an app with --preset", "switch to --preset", and for building a design system or applying a DESIGN.md or brand spec to shadcn/ui.