SkillVaultskills Browse all 1,000+ skills

Data · Version 1.4.0 · Reviewed 2026-08-02

Data Contract Breach Responder

Make data systems more correct and operable for breach detection and containment with evidence, explicit trade-offs, and a verification plan.

4 method steps 4 documented failure modes 4 diagnostic checks 7 quality gates

Responds to upstream contract violations with containment, downstream notification, and correction.

₹299 one-time

Get this skill archive

Install in your AI coding tool

SkillVault packages this skill in the open Agent Skills format for five leading coding tools, with a raw SKILL.md fallback for every other compatible IDE or agent.

See the complete graphical installation and usage guide

What this skill helps you do

  • Breach detection
  • Containment
  • Downstream correction

How Data Contract Breach Responder works

You provide

Schema, volumes, and the queries that actually run

It inspects

Access patterns and skew affecting breach detection

It decides

A containment design with migration ordering

You verify

Row counts and checksums compared before cutover

What it checks first

Data Contract Breach Responder responds to upstream contract violations with containment, downstream notification, and correction. Use it when the work involves Breach detection, Containment, Downstream correction.

  1. The real access patterns, since schema quality is meaningless without the queries it serves.
  2. Cardinality, skew, and growth rate of the key columns.
  3. Consistency and freshness requirements per consumer.
  4. Whether the model preserves history or overwrites it, which determines what questions remain answerable.

Failure modes it recognizes

  • A schema optimized for writes that makes the dominant read pattern a full scan.
  • Skewed partitioning concentrating load on one node.
  • Nullable columns encoding several meanings, making every downstream query ambiguous.
  • A pipeline silently dropping late-arriving records and under-reporting totals.

Answers it will reject

  • Normalizing or denormalizing by preference rather than by measured access pattern.
  • Adding a column for each new requirement until the table encodes multiple entities.
  • Backfilling without a reconciliation check that proves completeness.

Decision rules it applies

  • Design from the read path backward for read-heavy systems.
  • Make invalid states unrepresentable with constraints rather than conventions.
  • Version the schema and treat consumer compatibility as a contract.

Evidence it asks for

  • Profile real query patterns and volumes before proposing a change.
  • Validate migrations with row counts, checksums, and spot comparisons.
  • Monitor freshness and completeness as first-class data-quality signals.

The method inside

  1. Establish what is actually true about breach detection from the supplied evidence, and mark what is missing.
  2. Identify the mechanism behind containment rather than restating the symptom.
  3. Choose the smallest defensible change for downstream correction, weighing impact, confidence, effort, and reversibility.
  4. Plan migration and observability before cutover

Deliverables

  • Breach detection assessment
  • Containment decision and action plan
  • Downstream correction verification checklist

Evidence requirements

  • Schema, access patterns, query plans, or event contracts
  • Volume, cardinality, retention, and freshness
  • Consistency, latency, and migration constraints

Quality gates

  • Every material claim traces to supplied evidence or is labeled as a hypothesis.
  • The response follows the declared deliverable contract.
  • No execution, access, measurement, or verification is invented.
  • Secrets and personal data are redacted rather than repeated.
  • The user receives a concrete independent verification step.
  • The relevant failure modes in this domain were considered rather than only the reported symptom.
  • No listed anti-pattern was recommended as a solution.

Example task

Input

An upstream team changed an enum value and it flowed into reporting before anyone noticed. What now?

Expected output

Containment first: stop the pipeline rather than letting more bad data land, because every additional hour widens the correction. Then quantify which downstream tables and dashboards consumed it, and correct with a restatement rather than a silent overwrite...

Boundaries and compatibility

Ideal for

  • Breach detection: produce a decision or artifact grounded in supplied evidence.
  • Containment: produce a decision or artifact grounded in supplied evidence.
  • Downstream correction: produce a decision or artifact grounded in supplied evidence.

Out of scope

  • Recommending indexes without a workload
  • Treating eventual consistency as universally acceptable

Agent compatibility

  • GitHub Copilot Agent Skills
  • Cursor Agent Skills
  • Claude Code Skills
  • OpenAI Codex Skills
  • JetBrains Junie Skills

Tool policy: Advisory by default. No tools are assumed. If the host provides tools, use read-only evidence gathering unless the user explicitly approves a scoped write or execution action.