broker-status-page-monitoring-integration SKILL.md skillA
broker-status-page-monitoring-integration 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-status-page-monitoring-integration@v2.0.0Pins v2.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-status-page-monitoring-integration/SKILL.md- Versions recorded
- 5
- Latest version
- v2.0.0, committed Sep 3, 2026
- First version recorded
- Jul 25, 2026
- Size
- 12,277 bytes
- Repository stars
- 50
- License
- Apache-2.0
Use when an order or feed failure raises the on-call question of whether the broker is down or your code is. Polls Atlassian Statuspage v2 summary feeds scoped to the components your order flow uses, and requires fresh positive evidence.
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
## When to Use Invoke this skill when an order submission fails, a WebSocket drops, or a REST call times out, and the on-call question is *is this the broker or is it us?* Answering it by hand costs minutes at exactly the wrong moment. This skill polls the broker's public Statuspage v2 feed, scopes the reading to the components your order flow actually uses, and returns a classification an incident pipeline can route on. The two wrong answers are expensive in opposite directions, and the whole design follows from that asymmetry: - Wrongly answering **"broker"** suppresses the ticket for a live bug in your own code and, in most deployments, trips a circuit breaker. The bug stays in production because the pager never fired. - Wrongly answering **"us"** sends an engineer to debug working code during a broker incident, when their attention is worth the most. So **each confident verdict requires positive evidence.** `EXTERNAL_BROKER_OUTAGE` requires fresh evidence of impairment; `INTERNAL_APPLICATION_BUG` requires fresh evidence of health. Everything else — no reading, a stale reading, an unreachable …
Read the whole file at its exact version.
How to install
mdr add himanshuj16/algo-trading-skills/broker-status-page-monitoring-integration@sha256:c84525b7ca489cf0The line at the top of this page pins the label v2.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_54gvxqtuy6pawsbq)
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 | |
|---|---|---|---|---|---|
| v2.0.0 latest | 2026-09-03 | 8527a51 | 12,277 B | A | view · diff |
| v2.0.0 | 2026-08-20 | 269df51 | 12,501 B | A | view · diff |
| v1.0.0 | 2026-08-07 | 89d1436 | 3,055 B | A | view · diff |
| v1.0 | 2026-07-30 | dfc60c7 | 3,053 B | A | view · diff |
| v1.0 | 2026-07-25 | 777afdb | 3,064 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 (12277 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_54gvxqtuy6pawsbq GET https://markdownregistry.com/api/v1/resolve?ref=himanshuj16/algo-trading-skills/broker-status-page-monitoring-integration GET https://markdownregistry.com/api/v1/blob/c84525b7ca489cf0eefa418b7205377d3f0ebcce931c0a8cba3ca8183d768b17
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.