Jeecg System
jeecgboot/skills
JeecgBoot 系统主数据查询与管理。Use when user asks to query/create/manage system master data, or says "查询角色", "查询用户", "查询部门", "查询字典", "创建字典", "创建角色", "查岗位", "查职务", "查租户", "查数据源", "查定时任务", "系统主数据", "query…
Define a data contract between a producer and consumers of a dataset/event/API.
Install Data Contract
$ npx skills add mohitagw15856/pm-claude-skills --skill data-contract -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitagw15856/pm-claude-skills data-contract --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/data-contract .claude/skills/data-contract && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "data-contract" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/data-contract into .claude/skills/data-contract/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "data-contract", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/data-contractType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mohitagw15856/pm-claude-skills --skill data-contract -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitagw15856/pm-claude-skills data-contract --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/data-contract .agents/skills/data-contract && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "data-contract" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/data-contract into .agents/skills/data-contract/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "data-contract", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill data-contract -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitagw15856/pm-claude-skills data-contract --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/data-contract .cursor/skills/data-contract && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "data-contract" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/data-contract into .cursor/skills/data-contract/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "data-contract", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mohitagw15856/pm-claude-skills.git --path skills/data-contract--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mohitagw15856/pm-claude-skills --skill data-contract -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitagw15856/pm-claude-skills data-contract --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/data-contract .gemini/skills/data-contract && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "data-contract" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/data-contract into .gemini/skills/data-contract/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "data-contract", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mohitagw15856/pm-claude-skills data-contractInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mohitagw15856/pm-claude-skills --skill data-contract -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/data-contract .github/skills/data-contract && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "data-contract" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/data-contract into .github/skills/data-contract/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "data-contract", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill data-contract -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mohitagw15856/pm-claude-skills data-contract --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/data-contract .opencode/skills/data-contract && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "data-contract" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/data-contract into .opencode/skills/data-contract/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "data-contract", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
data-contract- GitHub stars
- 1.4k
- Token cost
- ~924 tokens
- SKILL.md length
- 421 words
- Files
- 1
- Skills in repo
- 1,322
- Repo updated
- First seen
- Licence
- MIT
At a glance
Define a data contract between a producer and consumers of a dataset/event/API.
- Asked to write a data contract
- SKILL.md covers Required Inputs, Output Format, Quality Checks and Anti-Patterns, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Define a schema agreement
What it does
Data Contract is an agent skill from mohitagw15856/pm-claude-skills. 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.
Its SKILL.md is about 920 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Data & Analytics, covering Data governance. The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.
When your agent uses it
- Asked to write a data contract
- Define a schema agreement
- Stop a producer from silently breaking downstream consumers
Example prompts
- “/data-contract”
What it can do on your machine
Read from SKILL.md and the folder at commit 1cbf1f0. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Data Contract loads about 924 tokens when it runs. Until then it costs about 106 tokens; SKILL.md has 421 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 421 words, ~924 tokens.
Download SKILL.mdSave it as
.claude/skills/data-contract/SKILL.md (or your agent's skills folder).- name
- data-contract
- description
- 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.
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 timestamps, currency/units, what null means, how late-arriving data is handled, the grain/uniqueness.
3. Quality SLAs — the guarantees, measurable: freshness (e.g. updated by 06:00 UTC daily), completeness (no missing required fields), validity (values in range), uniqueness (PK unique). These are what consumers can rely on.
4. Ownership & support — who owns it, where to raise issues, on-call/response expectations.
5. Versioning & breaking changes — semver for the schema; what counts as breaking (removing/renaming a field, tightening a type, changing semantics) vs. non-breaking (adding optional fields); deprecation window before a breaking change ships.
6. Change process — how a change is proposed, who must sign off (affected consumers), and the notice period.
Show full SKILL.md (160 more words)Show less
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
- An owner and an issue/escalation path are named
Anti-Patterns
- 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
Based On
Data-contract practice — schema + semantics + measurable quality SLAs, semantic versioning, and producer/consumer change governance.
Example Trigger Phrases
- "Write a data contract."
- "Define a schema agreement."
- "Set data SLAs."
- "Stop a producer from silently breaking downstream consumers."
© mohitagw15856, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/data-contract of mohitagw15856/pm-claude-skills.
Open the folder on GitHubat commit 1cbf1f0
Compare with similar skills
Data Contract next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Data Contract this skillmohitagw15856/pm-claude-skills | 1.4k | — | ~924 | Automated safety check: Pass | MIT | |
| Jeecg Systemjeecgboot/skills | 239 | — | ~3.2k | Automated safety check: Pass | Apache-2.0 | |
| Openalgo Chart Indicatormarketcalls/openalgo-charts | 140 | — | ~3.4k | Automated safety check: Notes | Apache-2.0 | |
| Data Quality Frameworkswshobson/agents | 40k | 11 repos | ~1.1k | Automated safety check: Pass | MIT | |
| Tracing Downstream Lineageastronomer/agents | 451 | 1 repos | ~1.2k | Automated safety check: Pass | Apache-2.0 | |
| Tracing Upstream Lineageastronomer/agents | 451 | 1 repos | ~1.1k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Openalgo Chart Indicator
marketcalls/openalgo-charts
Add a built-in openalgo-charts indicator, restyle it, build a settings UI from its descriptor, or author a custom indicator with registerIndicator or the Tier-2 external-data contract.
Data Quality Frameworks
wshobson/agents
Sets up data quality checks with Great Expectations, dbt tests and data contracts, with checkpoints and pass-fail reports for pipelines.
Tracing Downstream Lineage
astronomer/agents
Trace downstream data lineage and impact analysis. An agent skill from astronomer/agents.
Tracing Upstream Lineage
astronomer/agents
Trace upstream data lineage. An agent skill from astronomer/agents.
Research Data Feasibility and Leakage Checks
Light0305/Light-skills
Finds usable public datasets, judges whether the data can support a research idea, and checks train and test splits for leakage before results are trusted.
More from mohitagw15856/pm-claude-skills
All 1,322 skills in this repoExit Waterfall
mohitagw15856/pm-claude-skills
Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.
Feature Prioritisation
mohitagw15856/pm-claude-skills
Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.
Freelance Rate
mohitagw15856/pm-claude-skills
Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.
Offer Comparison
mohitagw15856/pm-claude-skills
Compare two or more job offers as total-comp curves over four years — vesting cliffs, bonuses, 401(k) match, and the crossover year computed, not vibed.
Refinance Breakeven
mohitagw15856/pm-claude-skills
Compute the month a refinance actually starts saving money — payment delta, breakeven month, and total interest on both paths including the term-reset trap.
Rent Vs Buy
mohitagw15856/pm-claude-skills
Model rent-vs-buy honestly — year-by-year net position for both paths including the assumption everyone drops (the renter invests the difference), with a breakeven horizon instead of a verdict.
Related
Categories
Questions about Data Contract
What does Data Contract do?
Define a data contract between a producer and consumers of a dataset/event/API. Data Contract is an agent skill from mohitagw15856/pm-claude-skills. Define a data contract between a producer and consumers of a dataset/event/API.
When should I use Data Contract?
Data Contract fits situations like: asked to write a data contract; define a schema agreement; stop a producer from silently breaking downstream consumers.
How do I install Data Contract in Claude Code?
Run `npx skills add mohitagw15856/pm-claude-skills --skill data-contract -a claude-code`. Or copy the skill folder (skills/data-contract in mohitagw15856/pm-claude-skills) into .claude/skills/data-contract in your project. Claude Code loads it when a task matches its description.
How do I install Data Contract in Codex?
Run `npx skills add mohitagw15856/pm-claude-skills --skill data-contract -a codex`. Or copy the skill folder (skills/data-contract in mohitagw15856/pm-claude-skills) into .agents/skills/data-contract in your project. Codex loads it when a task matches its description.
Can I use Data Contract in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mohitagw15856/pm-claude-skills --skill data-contract -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/data-contract, .gemini/skills/data-contract, .github/skills/data-contract and .opencode/skills/data-contract in your project.
What does Data Contract need to run?
SKILL.md names no scripts, command-line tools or credentials: Data Contract is instructions for the agent only.
Does Data Contract access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Data Contract safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Data Contract use?
Data Contract is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Data Contract use?
About 924 tokens (SKILL.md is roughly 3.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Data Contract?
Skills that share tags, products or a category with Data Contract: Jeecg System (jeecgboot/skills, 239 stars), Openalgo Chart Indicator (marketcalls/openalgo-charts, 140 stars), Data Quality Frameworks (wshobson/agents, 40k stars) and Tracing Downstream Lineage (astronomer/agents, 451 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Data Contract?
mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,431 GitHub stars. The repository holds 1,322 skills in this directory. The repository was last updated on October 7, 2026.
Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.