mcpField
D
data-export-portability-review

data-export-portability-review

github.com/sylphxaiData & databases147 installsUpdated today
Repository

About data-export-portability-review

A skill for product-operations teams that converts data portability requests into a reviewable flow and package plan. It distinguishes export, migration, deletion, restore, and legal/privacy cases while accounting for authorization and retention.

Key features

  1. 01Request scope and authority assessment
  2. 02Portability flow mapping
  3. 03Data package and schema planning
  4. 04Risk controls and event schema

Use cases

  1. 01Planning user or admin data exports
  2. 02Reviewing migration and account deletion flows
  3. 03Defining retention and delivery controls

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/sylphxai/skills --skill data-export-portability-review

After installing, type/data-export-portability-reviewin Claude Code to confirm it loaded.

Bundled filesagents/openai.yamlreferences/data-portability-patterns.md

Details

From the project README

Data Export Portability Review

Use this skill to turn a recurring product-operations problem into a concrete, reviewable artifact instead of generic advice.

Workflow

  1. Identify requester, data owner, scope, authority, sensitivity, size, format, retention, and destination.
  2. Read references/data-portability-patterns.md.
  3. Map request, authorization, export generation, delivery, expiration, deletion/retention exceptions, and support review.
  4. Separate user export, admin export, backup restore, migration, account deletion, and legal/privacy requests.
  5. Produce a portability flow, schema plan, support copy, risk controls, and event schema.

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 export secrets, third-party private data, or other users’ data without authority.
  • Do not make deletion promises that backups, legal holds, billing records, or fraud evidence cannot satisfy.
  • Prefer machine-readable stable formats plus human-readable summaries where useful.
  • Escalate jurisdiction-specific privacy/legal requests to qualified owners.

Output format

Portability context:
Requester / scope / sensitivity:

Flow:
- <request state> -> <authorization/export/delivery/support action>

Data package plan:
| Data class | Format | Included | Excluded | Retention/deletion note |
| --- | --- | --- | --- | --- |

Risks and support copy:
- <risk/control/message>

Comments

Markdown supported