What do I need to use Data Contract?

The data asset; Producer & consumers; Schema; Quality expectations.

Is Data Contract free to use?

Yes — run it free in the browser playground (no API key needed for the sponsored trial, or bring any provider key), or install it into Claude Code, Cursor, ChatGPT and more via npx pm-claude-skills. MIT-licensed and open source.

Data Contract

Q: How do I know the Data Contract output is good?

The skill verifies itself against its own quality checks: Every field has a type, required-flag, and clear semantics (esp. timezone/units/null meaning); Quality SLAs are measurable (a number/time), not "should be fresh"; Breaking vs. non-breaking changes are explicitly defined; There's a deprecation window and a sign-off process for breaking changes.

🔵 Stable🕐 updated 2026-06-28 🔷 SkillSpec L3 pm-dataeng

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.

▶ Run it free — no key needed 📝 Grade your existing draft View SKILL.md ↗

What to give it

▸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.

✅ The bar it holds itself to

Every skill in this library self-verifies — these are this skill's own quality checks, straight from its definition.

✓Every field has a type, required-flag, and clear semantics (esp. timezone/units/null meaning)

✓Quality SLAs are measurable (a number/time), not "should be fresh"

✓Breaking vs. non-breaking changes are explicitly defined

✓There's a deprecation window and a sign-off process for breaking changes

✓An owner and an issue/escalation path are named

⚠️ What it refuses to do

Do not leave semantics implicit — undocumented timezone/units/null handling is the #1 silent data bug

Do not write vague SLAs — "fresh and accurate" is unenforceable; give times and thresholds

Do not allow breaking changes without notice — a deprecation window + consumer sign-off is the whole point

Do not skip ownership — an unowned dataset has no one to hold to the contract

Do not version informally — schema changes need semver so consumers know what broke

Install

npx pm-claude-skills add --agent claude   # or codex · cursor · gemini · hermes
# or one-line MCP (every skill, any client):
claude mcp add pm-skills -- npx -y pm-claude-skills-mcp

Related skills

🔌 Embed this skill

Drop this on your blog, docs, or site — it renders a "Run this skill" card:

<div data-pm-skill="data-contract"></div>
<script src="https://mohitagw15856.github.io/pm-claude-skills/embed.js" async></script>

💬 Discussion

Data Contract is one of 599 open-source professional AI agent skills — all SkillSpec L3. Try them all in the browser · ⭐ Star on GitHub · Browse the full catalog