cross-datacenter-clock-sync-validation SKILL.md skillA
cross-datacenter-clock-sync-validation 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/cross-datacenter-clock-sync-validation@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/cross-datacenter-clock-sync-validation/SKILL.md- Versions recorded
- 5
- Latest version
- v2.0.0, committed Sep 3, 2026
- First version recorded
- Jul 25, 2026
- Size
- 8,279 bytes
- Repository stars
- 50
- License
- Apache-2.0
Use when a strategy merges ticks from more than one datacenter (NY4, LD4, a cloud region) and must prove those sites agree closely enough to order events correctly. Measures pairwise inter-region drift with its uncertainty and fails closed.
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
Use this skill when a strategy or arbitration module consumes ticks from **more than one
datacenter** and orders them against each other — Chicago CME against Equinix NY4, NY4
against LD4, one cloud region against another. If the sites' clocks disagree by more than
the tick-arrival spread, cross-region ordering inverts ($t_{\text{LD4}} < t_{\text{NY4}}$
for an event that genuinely happened later), and the strategy sees phantom latency
arbitrage and a corrupted book.
`CrossDatacenterClockSyncValidator` takes a simultaneous snapshot of per-node clock
telemetry, computes drift for every unordered pair, carries the measurement uncertainty
alongside the point estimate, and returns a **fail-closed** verdict in
`is_arbitration_allowed`.
## When NOT to Use
- **As a measure of divergence from UTC.** This measures sites against *each other*. Two
clocks that agree perfectly can both be 10 ms from UTC. Per-host UTC divergence and the
latched halt that must follow a breach are `clock-drift-monitoring-alerting-thresholds`.
- **As evidence of MiFID II RTS 25 compliance.** RTS 25 bounds each business clock against
…Read the whole file at its exact version.
How to install
mdr add himanshuj16/algo-trading-skills/cross-datacenter-clock-sync-validation@sha256:acdadf789b76de5dThe 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_lrfydbzexrw6uxlj)
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 | 8,279 B | A | view · diff |
| v2.0.0 | 2026-08-23 | b680e6a | 8,350 B | A | view · diff |
| v1.0.0 | 2026-08-07 | 89d1436 | 3,184 B | A | view · diff |
| v1.0 | 2026-07-30 | dfc60c7 | 3,182 B | A | view · diff |
| v1.0 | 2026-07-25 | 5767ba8 | 3,194 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 (8279 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_lrfydbzexrw6uxlj GET https://markdownregistry.com/api/v1/resolve?ref=himanshuj16/algo-trading-skills/cross-datacenter-clock-sync-validation GET https://markdownregistry.com/api/v1/blob/acdadf789b76de5d0c307db2081c8082770719fd65dc9fc6834c685397bc2485
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.