agentsclimarketplace
Sign in

Data contract design

Skill shinzoxD/knackbox/skills/data/data-contract-design

Define producer-consumer data contracts with schema evolution, compatibility, and SLAs. Use whenever the user designs event schemas, warehouse contracts, schema registry rules, or breaking-change policy between data producers and consumers.From its SKILL.md

Install
npx -y skills add shinzoxD/knackbox --skill data-contract-design

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its file declares

Copied from the file, not written here

The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

1.7 KB, 289 tokens by cl100k_base, as published. Nobody here has run it

Data Contract Design

A data contract is a promise: schema, semantics, freshness, and ownership. Evolution needs compatibility rules, not silent field renames.

Workflow

  1. Producers, consumers, grain, keys, and sensitivity (PII).
  2. Schema: required fields, types, enums, nullability.
  3. Semantics: units, timezones, late data, idempotency keys.
  4. SLA: freshness, completeness, support channel.
  5. Compatibility mode (backward/forward/full) and versioning.
  6. Validation in CI/pipeline; quarantine bad events.
  7. Change process: RFC, dual-publish, deprecation window.

Output format

## Contract: <name>
**Owner:** …
**Grain / keys:** …
### Schema
### Semantics
### SLA
### Compatibility & versioning
### Validation
### Consumers

Rules

  1. Never silently remove/rename required fields.
  2. Document unknown/forward-compatible extension points.
  3. PII fields need retention and access notes.
  4. Consumers should not parse free-text as schema.
  5. Dual-write windows for breaking changes.
  6. Mark assumptions about registry tech.

Edge cases

  • Fan-out many consumers: stricter stability.
  • Stream vs batch: different lateness policies.
  • Schema-less JSON: still define a contract envelope.

What ships with it: 1 file

1.2 KB alongside SKILL.md

benchmarks/

Keep looking

Skills are one crate of 326,422. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.