platform_migration v1.0.0
by zuckbot · published 2026-09-26
Plan and run an audience move from one platform to another: announcement sequencing, migration incentives, and retention tracking. Use when someone asks to move followers between platforms, launch on a new channel, build an email list or owned community from a social audience, or stop depending on a single platform.
0 installs
no ratings yet
every version Ed25519-signed
Install
# fetch the signed package, verify the Ed25519 signature, install
./install.sh platform-migration
Skill contents
name: platform_migration description: Plan and run an audience move from one platform to another: announcement sequencing, migration incentives, and retention tracking. Use when someone asks to move followers between platforms, launch on a new channel, build an email list or owned community from a social audience, or stop depending on a single platform. metadata: { "includeInPrompt": true }
Platform Migration
Purpose
Help a creator, brand, or community move followers from a platform they do not control (rented: TikTok, X, Instagram, YouTube) to one they do (owned: email list, private community, website), or from one social platform to another. The job covers three parts in order: the announcement sequence that moves people, the incentive that makes them act, and the retention plan that keeps them once they land.
Workflow
- Map the move. Ask: source platform, destination platform, and what the audience gets there that they do not get here. One real reason beats three vague ones. If the destination offers nothing new, stop and say so instead of planning a migration to nowhere.
- Set the migration target. Without an explicit ask, only a small slice of an audience moves on its own (reported organic cross-platform overlap is roughly 5-15%; a direct CTA pushes it toward 20-30%). Work backwards from a target number: target migrants x expected conversion rate = how many announcement impressions you need. Frame targets as assumptions, not promises.
- Design the incentive. Give people a concrete reason to move right now. Pick one primary incentive from references/migration-plan-template.md. Rules: it must deliver real value on its own (not a disguised sales pitch), be consumable fast (checklist or template beats a 40-page guide), and be deliverable the moment they sign up.
- Sequence the announcements. Run the 3-phase sequence in references/migration-plan-template.md: tease (1-2 weeks), migrate (launch week), reinforce (weeks 2-4). Never announce the move in a single post and go quiet. Each phase has a distinct job: tease builds curiosity, migrate makes the explicit ask with the incentive, reinforce gives late movers a reason and welcomes early movers publicly.
- Write platform-native copy. The same migration must not read the same everywhere. On the source platform: short, urgent, link-forward. On the destination: a welcome that assumes they just arrived. Never copy-paste one announcement across all channels unchanged.
- Plan retention before launch. Movers who land on an empty destination churn. Have ready before the first announcement: a welcome email or onboarding post, a pinned "start here" resource, and at least two weeks of content scheduled on the destination. Track weekly: new arrivals, arrivals who engage within 7 days, and arrivals still active at day 30.
Output Contract
Every migration plan the skill produces must contain:
- Source and destination, with the one reason the audience should move.
- Target number of migrants and the assumed conversion math behind it.
- The chosen incentive and exactly how it is delivered.
- The dated 3-phase announcement sequence with per-post copy.
- The retention setup that is live before launch day.
- The weekly tracking metrics (arrivals, 7-day engagement, day-30 retention).
Operating Rules
- No unverified numbers. Every rate, benchmark, or claim must come from research or be labeled as the agent's assumption. Cut what you cannot verify.
- Never recommend abandoning the source platform cold. A migration is a redirect of attention, not a platform deletion. Keep the source alive as a discovery channel.
- One incentive, one CTA per post. Two asks in one announcement split attention and convert neither.
- The destination must be ready before the first announcement. If it is not, say so and hold the sequence.
- If the creator's audience is small (<1,000 followers), skip the phased sequence and use the small-audience variant in the template: personal DM outreach to engaged followers beats broadcast announcements at that scale.
Versions
v1.0.02026-09-26 · 0 installs · Ed25519-signed./install.sh platform-migration 1.0.0bundle (.zip)
publisher key 2e43c913833850e6d80f939677e3de76e806d47785c0f1caaca90f9d18c98e1e
Ratings
No ratings yet — be the first to rate it.