1---2name: x-twitter-migration-assistant3description: Use when tasks require x twitter migration assistant with credential-aware preflight, deterministic execution, validation gates, and handoff-ready artifacts.4metadata:5 source: https://skillmd.com/skills/zwright8/x-twitter-migration-assistant6---78# X Twitter Migration Assistant910## Quick Reference11| Field | Value |12| --- | --- |13| Skill ID | `780` |14| Provider | `X Twitter` |15| Operation | `Migration Assistant` |16| Domain | `External SaaS integrations` |17| Runtime archetype | `migration-engine` |18| Core method | `staged migration planning and cutover` |19| Primary artifact | `x-twitter-migration-cutover-plan` |20| Routing tag | `x-twitter:migration-assistant` |21| Mutating | `yes` |22| Release cycles | `3` |2324## Why This Skill Exists25We need this skill because X Twitter workflows degrade when state changes are hard to undo once they begin. This specific skill turns X Twitter Migration Assistant into a deterministic, auth-checked workflow for plans and executes safe migrations to or from x twitter..2627## Trigger Checklist28- [ ] The task explicitly requires `X Twitter Migration Assistant` rather than generic brainstorming.29- [ ] The provider tenant, workspace, or environment is known before execution begins.30- [ ] Credential reuse has been checked before asking for new secrets.31- [ ] Success criteria, side effects, and handoff owner are clear.32- [ ] If the run mutates provider state, the relevant approval gates are available.3334## Auth & Access Profile35| Field | Value |36| --- | --- |37| External auth required | `yes` |38| API key likely required | `no` |39| Protocols | `HTTPS/REST` |40| Mutating | `yes` |41| Webhook capable | `no` |4243| Auth Mode | Kind | Env Hints | Validation |44| --- | --- | --- | --- |45| OAuth client or delegated session | `oauth2` | `X_TWITTER_CLIENT_ID`, `X_TWITTER_CLIENT_SECRET` | Reuse an active delegated session or validate the client credentials with a lightweight identity call. |46| Access token or personal access token | `token` | `X_TWITTER_TOKEN`, `X_TWITTER_ACCESS_TOKEN` | Validate the token with the smallest read-only endpoint that proves scope and tenancy. |4748## Inputs (contract)49| Input | Type | Required | Source |50| --- | --- | --- | --- |51| source inventory | signal | yes | operator or upstream tool |52| target mapping | signal | yes | operator or upstream tool |53| rollback plan | signal | yes | operator or upstream tool |5455## Outputs (contract)56| Output | Type | Guaranteed | Consumer |57| --- | --- | --- | --- |58| x-twitter-migration-cutover-plan | structured-artifact | yes | next workflow or operator |59| x-twitter-migration-cutover-plan-scorecard | scorecard | yes | reviewer |60| x-twitter-migration-cutover-plan-handoff | handoff-packet | yes | downstream owner |6162## Step-by-Step Implementation Guide631. Define the source inventory, target mapping, cutover window, and rollback checkpoint for X Twitter Migration Assistant before any X Twitter rehearsal is approved.642. Validate credential reuse, export baselines, and the human approval chain for every irreversible migration step.653. Implement plans and executes safe migrations to or from x twitter. as staged rehearsal, checkpoint, and cutover workflows that preserve a deterministic revert path.664. Capture migration inventories, mapping diffs, checkpoint identifiers, and partial-failure evidence in the cutover plan.675. Run simulation and regression suites that cover missing inventory, rollback weakness, and partial cutover outcomes.686. Publish a migration cutover plan with rehearsal status, rollback readiness, and the exact approval still required for production execution.6970## Operational Runbook71### Preflight72- Validate the full source inventory, target mapping, cutover window, and rollback checkpoint before rehearsal begins.73- Require an explicit human approval path for every irreversible step in the migration.7475### Execution76- Rehearse the migration with deterministic checkpoints before the production cutover is allowed.77- Pause on any unapproved mapping gap or rollback weakness rather than proceeding optimistically.7879### Recovery80- Abort cutover immediately when checkpoints or rollback evidence fail validation.81- Revert to the last stable platform state and capture every partially migrated object for review.8283### Handoff84- Return the migration cutover plan, rehearsal results, and rollback status.85- State clearly whether the migration is ready, blocked, partially rolled back, or awaiting approval.8687## Validation Gates & Test Matrix88| Gate | Purpose | On Fail |89| --- | --- | --- |90| auth-preflight | Validate credential presence, scope, and environment before work begins. | block execution |91| schema-contract-check | Ensure required signals and payload shapes remain valid. | quarantine and request correction |92| policy-approval-check | Verify the declared approval gates before mutating or publishing state. | pause or route to human review |93| reliability-check | Confirm retries, rollback, and checkpoint readiness. | rollback or fail closed |9495- Required validation suites: `unit`, `integration`, `simulation`, `regression-baseline`9697## Failure Modes & Recovery Playbook98| Code | Trigger | Action |99| --- | --- | --- |100| `E_INVENTORY_GAP` | The source inventory is incomplete or inconsistent with the target mapping. | Block rehearsal and request a corrected inventory or mapping diff. |101| `E_ROLLBACK_WEAKNESS` | Rollback checkpoints are missing or cannot restore all affected entities. | Fail closed and prohibit cutover approval. |102| `E_PARTIAL_CUTOVER` | The cutover succeeds for only a subset of the planned assets. | Abort the migration and revert to the last stable platform state. |103104## Tool Call Implementation105- Reuse existing credentials first. Check environment variables, secure stores, and active sessions before prompting.106- Start with the smallest authenticated read or validation call that proves identity and scope.107- Preserve request, response, and approval traces in `x-twitter-migration-cutover-plan` so downstream owners do not need to rediscover context.108- If any auth, contract, or approval gate fails, halt execution and attach remediation guidance instead of guessing.109110## Credential Reuse Policy111- Reuse valid provider credentials by default and prefer tenant-scoped sessions over newly created secrets.112- Prompt for credentials only when they are missing, invalid, expired, or point at the wrong environment.113- For webhook flows, validate the signing secret against a known sample before accepting live traffic.114115## Guardrails116- safety: Do not permit cutover without a rehearsed rollback checkpoint and explicit approval. (`rollback-readiness-check`)117- quality: Require inventory-to-mapping reconciliation before rehearsal and again before cutover. (`inventory-reconcile`)118- reliability: Abort immediately on partial cutover and revert to the last stable platform state. (`cutover-abort-and-revert`)119120## Acceptance Checklist121- [ ] Credential preflight and scope validation completed successfully.122- [ ] Required validation suites ran and all fail-closed gates passed.123- [ ] x-twitter-migration-cutover-plan, scorecard, and handoff packet were produced.124- [ ] Any mutations, approvals, or rollbacks are reflected in the artifact bundle.125126## Anti-Patterns127- Do not ask for new credentials before checking reusable auth context.128- Do not skip the read-only or dry-run validation step for mutating work.129- Do not proceed when approval gates, signing secrets, or rollback checkpoints are missing.130- Do not hand off partial or ambiguous provider state as complete.131132## Handoff Contract133- **Produces:** `x-twitter-migration-cutover-plan`, execution scorecard, approval trace, and next actions.134- **Consumes:** `source inventory`, `target mapping`, `rollback plan`.135- **Readiness rule:** release only after auth, contract, approval, and reliability gates all pass.136- **Downstream hint:** route to `x-twitter:migration-assistant` consumers with approval and credential context attached.137138## Observability & Continuous Improvement139- SLO: >=99.9% successful runs per 7-day window140- Error budget: <=0.1% critical failures per 7-day window141- Alert triggers:142- credential validation failures exceed baseline143- schema or contract regressions persist for two consecutive runs144- critical posture or rollback events exceed tolerance145- Primary outcome metric: `migration completeness`146- Secondary metrics: `cutover risk`, `rollback success rate`147- Review cadence: `daily`