broker-api-versioning-migration-playbook SKILL.md skillA
broker-api-versioning-migration-playbook from himanshuj16/algo-trading-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add himanshuj16/algo-trading-skills/broker-api-versioning-migration-playbook@v3.0.0Pins v3.0.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- himanshuj16/algo-trading-skills
- Path
skills/broker-api-versioning-migration-playbook/SKILL.md- Versions recorded
- 5
- Latest version
- v3.0.0, committed Sep 3, 2026
- First version recorded
- Jul 25, 2026
- Size
- 14,717 bytes
- Repository stars
- 50
- License
- Apache-2.0
Use when moving live order flow from one broker API version to the next: shadow reads, deterministic per-order canary routing that survives retries, latched rollback, and a translator that refuses to silently change time-in-force.
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
# Broker API Versioning & Migration Playbook ## When to Use Invoke this skill when a live trading system must move from one broker API version to another — a REST v1→v2 cutover, a new FIX session profile, an SDK major bump that changes payload shapes, or a forced migration off an endpoint with a published sunset date. It covers the migration *mechanism*: which version each request goes to, how read equivalence is proved before writes move, and how the cutover is aborted. The migration window is the dangerous part, not the destination. During it, two API versions are simultaneously live against the same account, and every ordinary failure — a timeout, a retry, a redeployed replica — can now resolve onto a *different version* than the one that saw the original request. The three rules below exist because each has a specific way of putting two orders in the market where the strategy intended one: > **A retry must reach the same version as the original attempt.** > **A cancel must reach the version that holds the order.** > **A target-version field you have not read in the spec does not exist.** …
Read the whole file at its exact version.
How to install
mdr add himanshuj16/algo-trading-skills/broker-api-versioning-migration-playbook@sha256:e215c3a0eb3b2d82The line at the top of this page pins the label v3.0.0, 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_cb7xfxspyvx3r4sy)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Jul 25, 2026 and Sep 3, 2026, about one every 10 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v3.0.0 latest | 2026-09-03 | 8527a51 | 14,717 B | A | view · diff |
| v3.0.0 | 2026-08-14 | 7eef45d | 14,816 B | A | view · diff |
| v1.0.0 | 2026-08-07 | 89d1436 | 2,561 B | A | view · diff |
| v1.0.0 | 2026-07-30 | dfc60c7 | 2,559 B | A | view · diff |
| git:20260725.777afdb | 2026-07-25 | 777afdb | 2,081 B | A | view |
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 (14717 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
himanshuj16/algo-trading-skills · 50 stars · license Apache-2.0 · pushed 2026-09-14 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_cb7xfxspyvx3r4sy GET https://markdownregistry.com/api/v1/resolve?ref=himanshuj16/algo-trading-skills/broker-api-versioning-migration-playbook GET https://markdownregistry.com/api/v1/blob/e215c3a0eb3b2d824e501f5decabc723a64f91ef9c336d114f4f4642c4d37263
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.