options-strategy SKILL.md skillA
options-strategy from iman/agent-driven-options-desk-and-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add iman/agent-driven-options-desk-and-skills/options-strategy@git:20260905.cc7d367Pins git:20260905.cc7d367 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- iman/agent-driven-options-desk-and-skills
- Path
plugins/option-desk/skills/options-strategy/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260905.cc7d367, committed Sep 5, 2026
- First version recorded
- Aug 31, 2026
- Size
- 7,660 bytes
- Repository stars
- 11
- License
- a license file GitHub does not identify
Build and compare multi-leg option structures from a chain: iron condors, iron butterflies, call butterflies, vertical spreads both debit and credit including bull put and bear call spreads, straddles, strangles, covered calls, cash-secured puts, protective puts, and the two-expiry family of calendars, diagonals and ratio diagonals. Produces legs, breakevens, maximum gain and loss, reward to risk, model probability of profit, net position Greeks and an estimate of what the round trip costs at…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Option strategies Three commands. Build one structure, list what exists, or compare them all. ## Execution route Prefer `option_strategy_build` to list or build structures and `option_strategy_compare` to compare them. Use `option_chain_snapshot` first when a fresh chain is needed. If the user has attached a CSV or JSON chain, pass its path as `source_path` for a local file. For remote chat, pass its content as `source_data` or `source_text`. Do not ask the user for it again. If a matching MCP tool is not available, use the `optiondesk` commands below. If neither MCP nor the CLI is available, say that no fresh structure analysis can be produced; do not invent figures or present example or remembered values as current. ## User-supplied data Before you send data to the tool, ask the user to state that private analysis is permitted. Then set `rights_confirmed` to true and name `data_source`. The local desk does not gate on that name: any `data_source` is accepted, so whether that provider's terms allow the analysis is the user's responsibility (only the hosted service refuses Yahoo, yfinance and personal Alpha Vantage data). …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_2atginee3yw2ez4z/44782aa01067aa5ea607780c50fed34d847a1c9b7167a7112cc7ea69e3ffc68a.json
Then /plugin install options-strategy@markdownregistry-2atginee3yw2ez4z in Claude Code. It installs git:20260905.cc7d367, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add iman/agent-driven-options-desk-and-skills/options-strategy@sha256:44782aa01067aa5eThe line at the top of this page pins the label git:20260905.cc7d367, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_2atginee3yw2ez4z)
1 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in iman/agent-driven-options-desk-and-skills/options-strategy since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of options-strategy from somewhere else? Ask it: where did my options-strategy come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 5 versions of this file, between Aug 31, 2026 and Sep 5, 2026, about one every day.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260905.cc7d367 latest | 2026-09-05 | cc7d367 | 7,660 B | A | view · diff |
| git:20260902.060fb4c | 2026-09-02 | 060fb4c | 7,422 B | A | view · diff |
| git:20260902.ade6800 | 2026-09-02 | ade6800 | 6,100 B | A | view · diff |
| git:20260831.ed610db | 2026-08-31 | ed610db | 5,973 B | A | view · diff |
| git:20260831.9feb0ec | 2026-08-31 | 9feb0ec | 4,507 B | A | view |
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/options-strategy/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (7660 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
iman/agent-driven-options-desk-and-skills · 11 stars · license a license file GitHub does not identify · pushed 2026-11-10 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_2atginee3yw2ez4z GET https://markdownregistry.com/api/v1/resolve?ref=iman/agent-driven-options-desk-and-skills/options-strategy GET https://markdownregistry.com/api/v1/blob/44782aa01067aa5ea607780c50fed34d847a1c9b7167a7112cc7ea69e3ffc68a
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from iman/agent-driven-options-desk-and-skills
Every file in iman/agent-driven-options-desk-and-skills