Skip to content
Skills Library
Data & analytics · Planning

contract

/contract

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.

Licence
MIT
Last repository change
06.11.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 06.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

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.

Arguments

/contract [source]
Original author description

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.

How it works

  1. Steps
  2. Output
  3. Reads
  4. Writes
  5. Never
Original SKILL.md headings · 36 lines, 322 words
SKILL.md preview
---
name: contract
description: 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.
argument-hint: "[source]"
---

# 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

1. Start from the profile of the source: every finding marked for the contract.
2. The format the source delivers: one delimiter, one encoding, one date format, one decimal separator, one null token.
3. The schema: take the tables, columns, types, keys and descriptions from the metadata file, never retype them. Mark the required columns.
4. The quality rules the source agrees to: unique keys, no empty required columns, values in range.
5. The delivery: how often, by what time, full or only the changes, and how a deleted row is marked.
6. The owner and the support channel on the source side.
7. The change process: the version of the contract, and how many days before a change the source announces it.
8. Write it in the Open Data Contract Standard, one file per source, and validate it against the schema of the standard.
9. List the open points for the meeting with the source owner.

## Output

One YAML file per source, like [references/purchasing.odcs.yaml](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.
Files in this package (2)
  • SKILL.md 2 KB
  • references/purchasing.odcs.yaml 4 KB

Versions

RepositoryScoreLicence
This page · DataWithBaraa/claude-code-data-engineering-skills90MIT
scalus3/scalus100Apache-2.0
langwatch/langwatch100Apache-2.0
railly/skills100MIT

Database snapshot: 13.11.2026 · package version 18c185de5fd9 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100data-contract
    Use when a table or dataset is consumed by others and must not break silently - define a data contract (schema, keys, nulls, allowed values, freshness SLA, owner) and generate the tests that enforce it in the pipeline. Also when the user asks for data quality rules, schema…
  • 100odcs-contracts
    Use when writing, validating or changing a data contract, or when a dataset needs its schema, quality rules, SLAs or personal-data classification defined. Works in ODCS v3.2.0 (Open Data Contract Standard) YAML, treats the contract as the source of truth, and keeps dbt models in step with it.
  • 90profile
    Use when a new source or new files arrive, to profile them before any data contract or pipeline code is written, the file formats, the schema, the data quality, the bad records, the relationships, the gaps and the personal data.
  • 90data-quality-and-contract-testing
    Drives data implementation with contracts, assertions, and validation evidence. Use when adding or changing ingestion logic, transformations, schemas, or published data products.
  • 90data-quality-gates
    Use when deciding which data quality checks a model, source or pipeline needs and whether each one blocks publication or only warns: freshness, schema, keys, volume anomalies and business-rule tests.
  • 100schema-contract
    Declare a data contract for a feed or table (CSV rows, list of dicts, JSON lines) and enforce it - per-column type (int/float/str/bool/date/ISO datetime), required/nullable, range, enum, regex, unique single or composite key, monotonic timestamps per key, max gap between…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.