shine-data-contract

Drafts auditable data contracts with schema, SLA, and versioning for event streams and BI marts.

1|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/diShine-digital-agency/SHINE-Code-System --skill shine-data-contract
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shine-data-contract
Source: https://github.com/diShine-digital-agency/SHINE-Code-System/tree/main/skills/shine-data-contract
Command: npx skills add https://github.com/diShine-digital-agency/SHINE-Code-System --skill shine-data-contract

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Drafting data contracts between producers and consumers to formalize data sharing, ownership, and governance, ensuring clear expectations and compliance.

Core Features & Use Cases

  • Define data ownership, schema, semantics per field, and SLA metrics for data products.
  • Capture breaking change policies and versioning to maintain stable integrations.
  • Facilitate governance and compliance through auditable contracts for event streams and BI pipelines.

Quick Start

Draft a data contract for a given data product outlining data owner, schema, field semantics, SLA, breaking changes policy, versioning, and on-call contact.

Frequently Asked Questions about shine-data-contract

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is a data contract and how does it formalize data ownership between producers and consumers?

A data contract is a formal agreement between producers and consumers that documents data ownership, schema, and field semantics. It establishes clear expectations for data sharing and ensures compliance through auditable change history.

How do I draft a data contract for an event stream or BI mart?

Draft a data contract by detailing the data owner, schema, field semantics, SLA metrics, breaking changes policy, versioning rules, and on-call contact. This formalizes data sharing for event streams and BI pipelines.

Does a data contract support Avro and Protobuf schema definitions?

Yes, drafting a data contract satisfies requirements for Avro or Protobuf-style schemas. It captures explicit semantics and versioning to maintain stable integrations across event streams and BI data products.

How do data contracts handle breaking changes and schema versioning?

Data contracts handle breaking changes by capturing explicit breaking change policies and versioning rules. This maintains stable integrations and provides an auditable change history for all data products.

What SLA and contact information should I include in a data contract?

Include SLA metrics and on-call contact information in your data contract to define data ownership and operational expectations. This ensures clear accountability between producers and consumers.