Compare
Data Contracts: 13 options
13 options compared · 4 tutorial, 2 skill, 2 runbook, 1 plugin, 1 hook, 1 agent, 1 template, 1 pattern
Comparing 13 options
Data Contracts — Versioned producer/consumer agreements: schema, semantics, SLAs and breaking-change policy. The registry currently holds 13 resources: 4 tutorials, 2 skills, 2 runbooks, 1 plugin, 1 hook, 1 agent, 1 template, 1 pattern.
Side by side
Every field below comes from the curated record — nothing is sponsored or ranked by payment:
| Resource | Type | Difficulty | Verification | Score |
|---|---|---|---|---|
| Schema Change Contract Review | Skill | intermediate | community | 40.5 |
| Data Contract Author | Skill | intermediate | community | 38.5 |
| Schema drift | Runbook | intermediate | community | 34.75 |
| Contracts as a Quality Gate | Pattern | intermediate | community | 34.75 |
| Author your first data contract | Tutorial | beginner | community | 34.15 |
| Enforce contracts in CI with the schema change check | Tutorial | beginner | community | 34.15 |
| Respond when a data contract breaks | Tutorial | intermediate | community | 34.15 |
| Review a schema change against its contract | Tutorial | intermediate | community | 34.15 |
| Contract Kit | Plugin | intermediate | community | 34.1 |
| Schema Reviewer | Agent | intermediate | community | 33.5 |
| Data Contract Template | Template | intermediate | community | 33.1 |
| Data contract broken | Runbook | intermediate | community | 32.75 |
| Schema Change Check | Hook | intermediate | community | 32.1 |
Trust breakdown
Verification mix: 13 community. No evidence gaps: every claim on file matches the record. Read how verification works — nothing here is independently audited yet, and the site says so everywhere it matters.
Security posture
Flagged entries: Schema Change Contract Review (1), Data Contract Author (1), Schema drift (2), Contract Kit (2), Schema Reviewer (1), Data Contract Template (2), Data contract broken (2), Schema Change Check (2). Flags record declared capabilities (credentials, write access, network calls) — they are facts to review, not verdicts. Every entry also passes the 30-rule static trust scan; findings print on each detail page.
How to choose
How to choose: start with Author your first data contract, Enforce contracts in CI with the schema change check for the gentlest on-ramp; Weight verification and evidence over score when two entries are close, and check the last-verified date on each page — the registry re-checks every 180 days.