mcpField
D
data-residency-region-review

data-residency-region-review

github.com/sylphxaiSecurity138 installsUpdated today
Repository

About data-residency-region-review

A skill for turning data residency and regional architecture questions into a review artifact with decisions, owners, gates, metrics, and recovery paths. It guides teams through data classification, transfer and access boundaries, evidence, and customer proof while requiring approved architecture and legal or compliance review.

Key features

  1. 01Residency and regional scope inventory
  2. 02Classification of data types
  3. 03Transfer and access control planning
  4. 04Recovery, migration, and monitoring decisions
  5. 05Evidence and customer proof planning

Use cases

  1. 01Reviewing a proposed regional data architecture
  2. 02Preparing evidence for customer residency questions
  3. 03Assessing failover, support access, and subprocessors
  4. 04Creating a residency control checklist

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/sylphxai/skills --skill data-residency-region-review

After installing, type/data-residency-region-reviewin Claude Code to confirm it loaded.

Bundled filesagents/openai.yamlreferences/data-residency-region-patterns.md

Details

From the project README

Data Residency Region Review

Use this skill to convert data residency, regional architecture, replication, subprocessor, support access, and compliance-proof questions into a concrete artifact with owners, gates, metrics, and recovery paths.

Workflow

  1. Identify customer commitments, regions, data classes, systems, subprocessors, backups, logs, analytics, AI processing, support access, failover needs, and contractual/regulatory constraints.
  2. Read references/data-residency-region-patterns.md.
  3. Classify data as customer content, metadata, billing, telemetry, support data, logs, backups, derived analytics, AI input/output, or admin audit record.
  4. Define residency boundary, allowed transfers, regional services, access controls, replication, backup/restore, deletion, migration, monitoring, and evidence.
  5. Produce residency design, state machine, decision table, event schema, control checklist, and customer proof plan.

When not to use

  • Do not use for generic advice the base model already handles without this skill's specific artifact contract.

Guardrails

  • Do not promise residency unless storage, processing, backups, logs, analytics, support access, and subprocessors match the claim.
  • Do not ignore metadata, telemetry, derived data, search indexes, AI inputs, or admin audit logs when defining region scope.
  • Do not make failover or support access silently move restricted data outside the committed region.
  • Do not answer customer residency questions without approved architecture and legal/compliance review.

Output format

Residency context:
Audience / source of truth / risk boundary:

Regional data plan:
| Area | Decision | Evidence | Risk | Owner |
| --- | --- | --- | --- | --- |

Transfers, access, and evidence controls:
- <trigger> -> <policy, metric, edge case, support note>

Comments

Markdown supported