desk-setup · git:20260902.060fb4c · 2026-09-02 · sha256 7e7f1a83c7e45506
desk-setup git:20260902.060fb4cB
Immutable. This exact content never changes and is served at /api/v1/blob/7e7f1a83c7e45506.
No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_pdmroae4zdwmwymz/7e7f1a83c7e45506cce45013d937f37446c0f70946a9c7837db2ef18dc939088.json
Then /plugin install desk-setup@markdownregistry-pdmroae4zdwmwymz in Claude Code. It installs this exact version, the one graded B here, pinned to the commit it was graded at, and leaves it there.
--- name: desk-setup description: "Install and verify the option desk command line tools so the option_* MCP tools and the optiondesk commands actually work. Use when a desk skill reports that no fresh figures can be produced, when optiondesk is not found, when the MCP tools are missing or failing, when the plugin was installed but nothing runs, or when the user asks how to set this up. Not for analysing options; it only gets the tools working." --- # Getting the desk working The skills in this plugin describe a set of local tools. Installing the plugin gives you the instructions; it does not install the tools. This skill closes that gap. ## First, find out what is actually missing ``` optiondesk doctor ``` If that runs, read its output: it reports whether the analytics engine is present, which providers can answer, which credentials are configured without printing them, and where artifacts are written. Fix what it names and stop here. If the shell says `command not found`, continue. ## Install ``` curl -fsSL https://raw.githubusercontent.com/Iman/agent-driven-options-desk-and-skills/main/install.sh | bash ``` That creates a virtualenv at `~/.optiondesk`, installs the analytics engine and the shell, links `optiondesk` and `optiondesk-mcp` into `~/.local/bin`, copies the skills into both `~/.claude/skills` and `~/.agents/skills`, and registers the MCP server with every agent runtime it finds. Re-running is safe, and `./install.sh --uninstall` removes only what it created. Python 3.11 or newer is required. Yahoo needs no API key, but it remains disabled until the user accepts its local personal-use boundary. Use `--accept-yahoo-terms` only after the user reads Yahoo's terms. The flag does not permit hosting, business use, public display, or redistribution. ## The failure almost everyone hits `~/.local/bin` is not on the PATH. The installer creates the two commands there and warns rather than editing your shell profile, because editing somebody's profile without asking is worse than a warning. Check: ``` echo $PATH | tr ':' '\n' | grep -c "$HOME/.local/bin" ``` If that prints 0, add it to your shell profile: ``` export PATH="$HOME/.local/bin:$PATH" ``` Then open a new shell. This also matters to the MCP server, whose plugin entry names the bare command `optiondesk-mcp` and resolves it through PATH. ## Verify, in this order ``` optiondesk doctor engine, providers, credentials, paths optiondesk expiries SPY reaches the network and lists expiries optiondesk chain SPY writes the first artifact optiondesk greeks --band 0.06 computes from it ``` If `doctor` works and `expiries` does not, the problem is network or provider, not installation. If `chain` works and `greeks` reports the engine is unavailable, the engine did not install; re-run the installer without `--no-engine`. ## What to tell the user when it still will not work Say plainly that no fresh figures can be produced, and why. Do not substitute remembered or example numbers for a chain that was never pulled, and do not present a model value as a quote. A skill with no tools is a skill that explains the desk; it is not a desk. ## What this cannot fix In ChatGPT on the web or on a phone, there is no local process to install and nothing here will make local tools run. Do not ask the user to install a local process in that session. Use an attached remote MCP server when one is present. Without one, the skills can analyse user-provided data only. Hosted deployments must set `PUBLIC_DATA_MODE=demo` or `licensed`. Demo mode blocks all external providers. Licensed mode permits only a provider that has an explicit approval for public display, derived outputs, storage, and MCP delivery. Never change this mode to work around a provider refusal. ## Reporting rules They apply here too, briefly. Never present a remembered or example figure as a fresh one, and say plainly when the tools are absent rather than working around it. Never recommend a trade. The full terms are in DISCLAIMER.md, which ships beside this skill when it is installed from a package and sits at the repository root otherwise.