SkillVaultskills Browse all 500 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 5 documented failure modes 5 diagnostic checks 7 quality gates

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

₹149 one-time

Get this skill archive

What this skill helps you do

  • Breach detection
  • Containment
  • Downstream correction

How Data Contract Breach Responder works

You provide

Obligations, data inventory, and current controls

It inspects

Requirement type and implemented control for breach detection

It decides

A containment gap register with accountable owners

You verify

Each control mapped to evidence an auditor would accept

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. Whether the obligation is a legal requirement, a contractual commitment, or an internal policy — the escalation path differs.
  2. The specific data categories and lawful basis, rather than a general statement about compliance.
  3. Data flows across jurisdictions and processors, which determine transfer obligations.
  4. Retention and deletion behavior in every downstream copy, including backups and analytics.
  5. Who is accountable for the decision, since a compliance analysis without an owner is not actionable.

Failure modes it recognizes

  • Deletion implemented in the primary store while copies persist in backups, exports, logs, and warehouses.
  • Consent collected for one purpose and reused for another without a valid basis.
  • A subprocessor added without a data-processing agreement or customer notification.
  • Retention policy defined but never enforced by an automated job.
  • A control documented in policy but not implemented in the system it describes.

Answers it will reject

  • Providing a definitive legal conclusion rather than a structured analysis for qualified review.
  • Treating a compliance certification as evidence that a specific control works.
  • Relying on contractual language to mitigate a technical risk that is technically preventable.
  • Presenting risk without severity, likelihood, and the accountable owner.

Decision rules it applies

  • Separate legal requirement, contractual obligation, and internal policy in every finding.
  • Escalate to qualified counsel for anything that constitutes legal advice, and say so plainly.
  • Map every obligation to a specific implemented control and its evidence, or mark it as a gap.
  • Prefer technical enforcement over documented intent, because documented intent is not a control.

Evidence it asks for

  • Build a data inventory: category, source, purpose, basis, location, retention, and downstream copies.
  • Trace one deletion request end to end and enumerate every store it must reach.
  • Record the evidence artifact that would satisfy an auditor for each control.

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 custom agents
  • Claude Agent Skills / SKILL.md
  • Any instruction-following chat model

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.