cross-vendor-timestamp-precision-reconciliation SKILL.md skillA
cross-vendor-timestamp-precision-reconciliation 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-vendor-timestamp-precision-reconciliation@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-vendor-timestamp-precision-reconciliation/SKILL.md- Versions recorded
- 5
- Latest version
- v2.0.0, committed Sep 3, 2026
- First version recorded
- Jul 30, 2026
- Size
- 10,056 bytes
- Repository stars
- 50
- License
- Apache-2.0
Use when a pipeline ingests timestamps from several vendors in different units and encodings, normalising seconds, milliseconds, ISO-8601 and nanoseconds to integer nanosecond UTC and flagging precision loss and out-of-order arrivals.
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 pipeline ingests market data from more than one vendor and the timestamps arrive in different units and encodings (float seconds, integer milliseconds, ISO-8601 strings, int64 nanoseconds — e.g. Databento publishes int64 UTC nanoseconds since epoch). Mixing them without exact normalization produces mis-ordered tick sequences, phantom latency measurements, and precision claims a firm cannot support in a MiFID II RTS 25 clock-traceability review. This module converts every raw timestamp into a 64-bit integer nanosecond UTC epoch using **exact integer/Decimal arithmetic**, flags out-of-order arrivals, audits the precision tier actually delivered, and measures cross-vendor skew between records that describe the *same* event. ## When NOT to Use - **As a clock-synchronization monitor.** This engine compares timestamps *in data*. It cannot measure a host's offset from UTC — that is PTP/NTP telemetry; see `clock-drift-monitoring-alerting-thresholds` and `cross-datacenter-clock-sync-validation`. RTS 25 compliance is demonstrated with traceability evidence for the clock, not with a feed-comparison report. …
Read the whole file at its exact version.
How to install
mdr add himanshuj16/algo-trading-skills/cross-vendor-timestamp-precision-reconciliation@sha256:86b2078fa7d60881The 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_hsm7yrnphowzgcuh)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Jul 30, 2026 and Sep 3, 2026, about one every 9 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v2.0.0 latest | 2026-09-03 | 8527a51 | 10,056 B | A | view · diff |
| v2.0.0 | 2026-08-23 | b680e6a | 10,056 B | A | view · diff |
| v1.0.0 | 2026-08-07 | 89d1436 | 3,616 B | A | view · diff |
| v1.0.0 | 2026-07-30 | dfc60c7 | 3,614 B | A | view · diff |
| v1.0.0 | 2026-07-30 | 66d0ca2 | 3,631 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 (10056 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_hsm7yrnphowzgcuh GET https://markdownregistry.com/api/v1/resolve?ref=himanshuj16/algo-trading-skills/cross-vendor-timestamp-precision-reconciliation GET https://markdownregistry.com/api/v1/blob/86b2078fa7d608810e4d293ed37476ec51d268f7ab99fae944ae4d3166052bc7
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.