desk-setup SKILL.md skillB
desk-setup 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/desk-setup@git:20260908.9626273Pins git:20260908.9626273 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- B, 16 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- iman/agent-driven-options-desk-and-skills
- Path
shell/skills/desk-setup/SKILL.md- Versions recorded
- 3
- Latest version
- git:20260908.9626273, committed Sep 8, 2026
- First version recorded
- Aug 31, 2026
- Size
- 6,038 bytes
- Repository stars
- 11
- License
- a license file GitHub does not identify
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.
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
# 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 …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_ipsckbl6zq7w3aof/e173642cb9fde58f4814faff2ca2988a0e50902a085b7f241452b0b30b83ab85.json
Then /plugin install desk-setup@markdownregistry-ipsckbl6zq7w3aof in Claude Code. It installs git:20260908.9626273, the one graded B here, pinned to the commit it was graded at, and leaves it there.
mdr add iman/agent-driven-options-desk-and-skills/desk-setup@sha256:e173642cb9fde58fThe line at the top of this page pins the label git:20260908.9626273, 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_ipsckbl6zq7w3aof)
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/desk-setup 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 desk-setup from somewhere else? Ask it: where did my desk-setup 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 3 versions of this file, between Aug 31, 2026 and Sep 8, 2026, about one every 4 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260908.9626273 latest | 2026-09-08 | 9626273 | 6,038 B | B | view · diff |
| git:20260902.060fb4c | 2026-09-02 | 060fb4c | 4,178 B | B | view · diff |
| git:20260831.0345016 | 2026-08-31 | 0345016 | 3,616 B | B | 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/desk-setup/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
- fail: No curl or wget piped into a shell (matched: curl -fsSL https://raw.githubusercontent.com/Iman/agent-driven-options-desk-and-skills/main/install.)
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (6038 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 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
Starting a new one? Use a template for SKILL.md on mdpantry, which passes every one of these checks and says what to change in it.
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_ipsckbl6zq7w3aof GET https://markdownregistry.com/api/v1/resolve?ref=iman/agent-driven-options-desk-and-skills/desk-setup GET https://markdownregistry.com/api/v1/blob/e173642cb9fde58f4814faff2ca2988a0e50902a085b7f241452b0b30b83ab85
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