nw-cross-cutting-input-data-contracts SKILL.md skillA
nw-cross-cutting-input-data-contracts from nwave-ai/nwave is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add nwave-ai/nwave/nw-cross-cutting-input-data-contracts@git:20261102.c67d57bPins git:20261102.c67d57b in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- nwave-ai/nwave
- Path
nWave/skills/nw-cross-cutting-input-data-contracts/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261102.c67d57b, committed Nov 2, 2026
- Size
- 8,378 bytes
- Repository stars
- 633
- License
- MIT
KNOWLEDGE — use when adding data, declaring inputs, or choosing a join key.
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
# Input and Data Contracts **Composition:** Load with `nw-cross-cutting-invariants`; no forced sequence; return to its routing table for other concerns. ## `data:consumer-known-before-produced` — a datum is produced because we already know who needs it (STANDING) **A datum is justified only by a named consumer.** Before adding a field, an event, a config key, an artifact section, or a telemetry record, name **who reads it** and **through which mechanism**. No named reader → the datum is unjustified and must not be added. This is not bookkeeping hygiene: unread data is what makes a system incoherent, because every future reader must decide whether it means something and none can tell. **Second half, and it is the one that gets forgotten: name the JOIN KEY.** Knowing who reads a datum is not enough — it must be indexable against what the reader already holds. Two data both faithfully consumed, indexed on keys that do not meet, cannot be related: the information exists and is unusable. State the key the consumer will join on, at the moment you declare the field. Measured instances of the failure, all in this repository: | Datum | Declared | Consumed | |---|---|---| …
Read the whole file at its exact version.
How to install
mdr add nwave-ai/nwave/nw-cross-cutting-input-data-contracts@sha256:7a9b8f2d69b59af6The line at the top of this page pins the label git:20261102.c67d57b, 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_aetvtz2efllpobv4)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Nov 2, 2026.
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 (8378 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
nwave-ai/nwave · 633 stars · license MIT · pushed 2026-11-07 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_aetvtz2efllpobv4 GET https://markdownregistry.com/api/v1/resolve?ref=nwave-ai/nwave/nw-cross-cutting-input-data-contracts GET https://markdownregistry.com/api/v1/blob/7a9b8f2d69b59af6dcc8bda0ed274e5f58472d174910a16381ce10fed6bb5bc9
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.