contract
Skill84 starsChanged 14 days agoMITView on GitHub
Use when a new source is connected or a source changes how it delivers, to write the data contract with the source system, the format, the schema, the quality rules, the delivery, the owner and the change process.
6 other projects use a version of this.
Adopted by
Most recently taken up by
- Railly/skillstheir own version, first seen Nov 1, 2026
- mephistopheles4/grimoiretheir own version, first seen Oct 31, 2026
- aibtcdev/skillstheir own version, first seen Oct 26, 2026
- langwatch/langwatchtheir own version, first seen Oct 17, 2026
- DanaResearchGroup/agent-skillstheir own version, first seen Aug 26, 2026
- Gena915/central-braintheir own version, first seen Jul 16, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- langwatch/langwatch★ 5ksame name
- aibtcdev/skills★ 11same name
- Railly/skills★ 11same name
- DanaResearchGroup/agent-skills★ 1same name
- mephistopheles4/grimoire★ 1same name
- Gena915/central-brain★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository16 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- big-reviewSkill
- cost-reviewSkill
- data-productSkill
- docsSkill
- impactSkill
- incidentSkill
- knowledge-refreshSkill
- metadataSkill
- migrationSkill
- profileSkill
- pr-reviewSkill
- qualitySkill
- reconcileSkill
- test-dataSkill
- toolkitSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
Start from the profile of the source: every finding marked for the contract.
- Distinctive: line 22
Write it in the Open Data Contract Standard, one file per source, and validate it against the schema of the standard.
- Distinctive: line 39
Never sends the contract: the data engineer agrees it with the source owner.
- Distinctive: line 40
Never writes a transformation into the contract: it describes the data, and the pipeline is a separate change.
“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Contract
The job: the data contract between the data platform and one source system, written from the profile and the metadata, and agreed with the source owner. It holds facts and agreements, never steps and never SQL. The contract with the consumers of a table is part of the data-product skill.
Input: the name of the source, with its profile and its metadata.
Steps
- Start from the profile of the source: every finding marked for the contract.
- The format the source delivers: one delimiter, one encoding, one date format, one decimal separator, one null token.
- The schema: take the tables, columns, types, keys and descriptions from the metadata file, never retype them. Mark the required columns.
- The quality rules the source agrees to: unique keys, no empty required columns, values in range.
- The delivery: how often, by what time, full or only the changes, and how a deleted row is marked.
- The owner and the support channel on the source side.
- The change process: the version of the contract, and how many days before a change the source announces it.
- Write it in the Open Data Contract Standard, one file per source, and validate it against the schema of the standard.
- List the open points for the meeting with the source owner.
Output
One YAML file per source, like references/purchasing.odcs.yaml: the format, the schema with the keys and the required columns, the quality rules, the delivery, the owner, the support channel and the change process.
Reads
- the profile, the metadata, the documents of the source, the existing contracts
Writes
- the data contract of the source, and the list of open points
Never
- Never sends the contract: the data engineer agrees it with the source owner.
- Never writes a transformation into the contract: it describes the data, and the pipeline is a separate change.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.