data-contract
Define a data contract between a producer and consumers of a dataset/event/API. Use when asked to write a data contract, define a schema agreement, set data SLAs, or stop a producer from silently breaking downstream consumers. Produces a contract — schema with types & constraints, semantics, quality SLAs (freshness/completeness/validity), ownership, versioning & breaking-change policy, and a change process.
npx skills add mohitagw15856/pm-claude-skills --skill data-contract --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Data Contract Skill Most data outages are a producer changing a column without telling anyone downstream. A data contract fixes that: it's an explicit, versioned agreement on the **schema, semantics, and quality guarantees** of a dataset/event/stream, with an owner and a breaking-change policy. This skill writes one, so producers and consumers share a single source of truth and changes can't silently break pipelines. ## Required Inputs Ask for these only if they aren't already provided: - **The data asset** — the table, event, topic, or API, and what it represents. - **Producer & consumers** — who owns it, who depends on it. - **Schema** — fields, types, and which are required; the semantics of the tricky ones. - **Quality expectations** — freshness (how current), completeness, valid ranges, uniqueness. ## Output Format ### Data Contract: `[asset]` v[x.y] **Producer (owner):** [team] · **Consumers:** [teams/systems] · **Status:** active **1. Schema** — every field: name · type · required? · description/semantics · constraints (enum, range, format). | field | type | required | constraint | meaning | |---|---|---|---|---| **2. Semantics** — the non-obvious meanings: timezone of tim
- Required Inputs
- Output Format
- Data Contract: [asset] v[x.y]
- Quality Checks
- Anti-Patterns
- Based On
What does the data-contract skill do?
Define a data contract between a producer and consumers of a dataset/event/API. Use when asked to write a data contract, define a schema agreement, set data SLAs, or stop a producer from silently breaking downstream consumers. Produces a contract — schema with types & constraints, semantics, quality SLAs (freshness/completeness/validity), ownership, versioning & breaking-change policy, and a change process.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill data-contract --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.