Recipe Post Mortem Setup
googleworkspace/cli
Create a Google Docs post-mortem, schedule a Google Calendar review, and notify via Chat.
Move a team's files to a new platform without losing work or a week — the pre-migration freeze, the verified copy, the permissions remap, the cutover announcement, and the old-system read-only…
Install Migration Day Runbook
$ npx skills add mohitagw15856/pm-claude-skills --skill migration-day-runbook -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitagw15856/pm-claude-skills migration-day-runbook --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/migration-day-runbook .claude/skills/migration-day-runbook && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "migration-day-runbook" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/migration-day-runbook into .claude/skills/migration-day-runbook/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "migration-day-runbook", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/migration-day-runbookType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mohitagw15856/pm-claude-skills --skill migration-day-runbook -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitagw15856/pm-claude-skills migration-day-runbook --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/migration-day-runbook .agents/skills/migration-day-runbook && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "migration-day-runbook" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/migration-day-runbook into .agents/skills/migration-day-runbook/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "migration-day-runbook", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill migration-day-runbook -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitagw15856/pm-claude-skills migration-day-runbook --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/migration-day-runbook .cursor/skills/migration-day-runbook && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "migration-day-runbook" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/migration-day-runbook into .cursor/skills/migration-day-runbook/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "migration-day-runbook", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mohitagw15856/pm-claude-skills.git --path skills/migration-day-runbook--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mohitagw15856/pm-claude-skills --skill migration-day-runbook -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitagw15856/pm-claude-skills migration-day-runbook --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/migration-day-runbook .gemini/skills/migration-day-runbook && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "migration-day-runbook" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/migration-day-runbook into .gemini/skills/migration-day-runbook/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "migration-day-runbook", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mohitagw15856/pm-claude-skills migration-day-runbookInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mohitagw15856/pm-claude-skills --skill migration-day-runbook -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/migration-day-runbook .github/skills/migration-day-runbook && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "migration-day-runbook" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/migration-day-runbook into .github/skills/migration-day-runbook/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "migration-day-runbook", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill migration-day-runbook -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mohitagw15856/pm-claude-skills migration-day-runbook --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/migration-day-runbook .opencode/skills/migration-day-runbook && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "migration-day-runbook" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/migration-day-runbook into .opencode/skills/migration-day-runbook/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "migration-day-runbook", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
migration-day-runbook- GitHub stars
- 1.4k
- Token cost
- ~1.5k tokens
- SKILL.md length
- 745 words
- Files
- 1
- Skills in repo
- 1,348
- Repo updated
- First seen
- Licence
- MIT
At a glance
Move a team's files to a new platform without losing work or a week — the pre-migration freeze, the verified copy, the permissions remap, the cutover announcement, and the old-system read-only…
- Works in 5 steps: Freeze short, announce twice: the copy… → Verify by count and by sample:… → Permissions are a workstream, not a… → …
- Asked were moving from Dropbox to Drive
- SKILL.md covers What This Skill Produces, Required Inputs, Framework: The Edge Rules and Output Format, plus 8 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Migration Day Runbook is an agent skill from mohitagw15856/pm-claude-skills. Move a team's files to a new platform without losing work or a week — the pre-migration freeze, the verified copy, the permissions remap, the cutover announcement, and the old-system read-only afterlife. Use when asked we're moving from Dropbox to Drive, migrate our files to SharePoint, plan the file migration day, or how do we switch platforms safely. Produces the migration runbook: freeze window, copy-and-verify steps, permissions mapping, the cutover comms, and the rollback line.
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in DevOps & Cloud, covering Runbooks and postmortems and Cloud office suites. It works with Microsoft SharePoint and Dropbox. The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.
When your agent uses it
- Asked were moving from Dropbox to Drive
- Migrate our files to SharePoint
- Plan the file migration day
- How do we switch platforms safely
Example prompts
- “/migration-day-runbook”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Freeze short, announce twice: the copy happens inside a declared no-edits window (evening/weekend for most teams) — announced a week out…
- Verify by count and by sample: post-copy: file counts per top-level folder old-vs-new, total size within tolerance, and hand-checks of the…
- Permissions are a workstream, not a checkbox: inventory the old platform's shares (especially external ones), map to the new model, and…
- The cutover announcement answers exactly three questions: where do I go now (the link) · what happened to my stuff (same structure, here's…
- The old platform goes read-only, immediately: the afterlife rule — readable for the transition period (comfort + the missing-file safety…
What it can do on your machine
Read from SKILL.md and the folder at commit 1cbf1f0. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Migration Day Runbook loads about 1.5k tokens when it runs. Until then it costs about 127 tokens; SKILL.md has 745 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 745 words, ~1,457 tokens.
Download SKILL.mdSave it as
.claude/skills/migration-day-runbook/SKILL.md (or your agent's skills folder).- name
- migration-day-runbook
- description
- Move a team's files to a new platform without losing work or a week — the pre-migration freeze, the verified copy, the permissions remap, the cutover announcement, and the old-system read-only afterlife. Use when asked we're moving from Dropbox to Drive, migrate our files to SharePoint, plan the file migration day, or how do we switch platforms safely. Produces the migration runbook: freeze window, copy-and-verify steps, permissions mapping, the cutover comms, and the rollback line.
Migration Day Runbook Skill
File migrations fail at the edges, not the middle: work edited during the copy window (lost or forked), permissions that mapped wrong (the intern sees the comp sheet; Legal sees nothing), links across the company now pointing at a dead platform, and an old system left writable so half the team never leaves. The runbook handles the edges: a short announced freeze, copy with verification (counts and spot-checks, not vibes), a permissions remap done as its own workstream, cutover comms with the three answers everyone needs, and the old platform flipped read-only — the single move that makes migrations stick.
What This Skill Produces
- The runbook — phased: prepare → freeze → copy → verify → permissions → cutover → afterlife, each with owner and duration
- The verification plan — counts by folder, spot-restores, and the biggest-risk samples checked by hand
- The permissions remap — old-model groups/shares → new-model equivalents, with the deny-by-default posture for mismatches
- The comms set — the advance notice, the freeze reminder, and the cutover announcement with its three answers
Required Inputs
Ask for these if not provided:
- From → to, and the size — platforms, volume (GB and file count), and any known exotica (huge files, weird formats, apps writing into the old drive)
- The sharing surface — external shares, published links, and integrations pointing at the old platform; each is a breakage waiting for its line in the runbook
- The freeze tolerance — can the team stop editing for a day? A weekend? Never (then the delta-sync approach, stated)?
- The permission model gap — how sharing works old vs. new; the remap is where migrations quietly leak confidential files
Framework: The Edge Rules
- Freeze short, announce twice: the copy happens inside a declared no-edits window (evening/weekend for most teams) — announced a week out and the day before. Edits during the copy are the classic loss; the freeze is cheaper than the fork-hunt.
- Verify by count and by sample: post-copy: file counts per top-level folder old-vs-new, total size within tolerance, and hand-checks of the highest-stakes folders (Legal, Finance, the current projects). A migration is "done" when verification says so, not when the progress bar does.
- Permissions are a workstream, not a checkbox: inventory the old platform's shares (especially external ones), map to the new model, and where the models don't align, fail closed — over-restricting gets a complaint ticket; over-sharing gets an incident. External shares get re-issued deliberately, not bulk-recreated.
- The cutover announcement answers exactly three questions: where do I go now (the link) · what happened to my stuff (same structure, here's the map) · what do I do if something's missing (the named person, the SLA). Everything else is noise; these three prevent the help-desk flood.
- The old platform goes read-only, immediately: the afterlife rule — readable for the transition period (comfort + the missing-file safety net), writable never (or half the team quietly stays). A read-only banner pointing at the new home does more for adoption than any training session. Decommission date set now, calendar-reminded, executed after the retention check (document-retention-map).
Show full SKILL.md (249 more words)Show less
Output Format
Migration Runbook: [old] → [new], [date]
Phases
| Phase | When | Owner | Duration |
|---|---|---|---|
| [Prepare (inventory, permissions map, comms 1) · Freeze · Copy · Verify · Permissions · Cutover (comms 3) · Afterlife (read-only flip)] |
Verification Plan
[Counts per top folder · size tolerance · the hand-check list (highest-stakes folders) · the pass/fail line]
Permissions Remap
[Old shares inventory → new equivalents · fail-closed mismatches · external shares re-issued deliberately]
Comms
[T-7 notice · T-1 freeze reminder · cutover announcement: the three answers + the missing-file contact]
Rollback Line
[The condition that aborts (verification fails, permissions can't map) · rollback = unfreeze the old, reschedule — cheap because the old is untouched until read-only]
Quality Checks
- The copy happens inside an announced freeze
- Verification is counts + samples with a pass/fail line, before cutover comms
- Permission mismatches fail closed, external shares handled by hand
- The announcement answers exactly the three questions with a named missing-file contact
- The old platform is read-only from cutover, with a decommission date set
Anti-Patterns
- Do not copy a live drive — the freeze is one evening; the fork-hunt is one month
- Do not trust the progress bar as verification — counts and samples or it didn't happen
- Do not bulk-recreate external shares — each one re-issued is each one re-decided
- Do not leave the old platform writable "during transition" — that's two sources of truth, i.e., zero
- Do not skip the rollback line — a migration that can't abort will be pushed through broken
Example Trigger Phrases
- "We're moving from Dropbox to Drive."
- "Migrate our files to SharePoint."
- "Plan the file migration day."
- "How do we switch platforms safely?"
© mohitagw15856, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/migration-day-runbook of mohitagw15856/pm-claude-skills.
Open the folder on GitHubat commit 1cbf1f0
Compare with similar skills
Migration Day Runbook next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Migration Day Runbook this skillmohitagw15856/pm-claude-skills | 1.4k | — | ~1.5k | Automated safety check: Pass | MIT | |
| Recipe Post Mortem Setupgoogleworkspace/cli | 31k | — | ~256 | Automated safety check: Pass | Apache-2.0 | |
| Performing Cloud Storage Forensic Acquisitionmukul975/Anthropic-Cybersecurity-Skills | 34k | — | ~3.5k | Automated safety check: Pass | Apache-2.0 | |
| Spfx Releasepnp/docker-spfx | 134 | — | ~572 | Automated safety check: Notes | MIT | |
| Trader Memory Coretradermonty/claude-trading-skills | 3k | 2 repos | ~4.3k | Automated safety check: Pass | MIT | |
| Author Migrationnrwl/nx | 29k | — | ~12k | Automated safety check: Notes | MIT |
Similar skills
Performing Cloud Storage Forensic Acquisition
mukul975/Anthropic-Cybersecurity-Skills
Perform forensic acquisition of cloud storage services including Google Drive, OneDrive, Dropbox, and Box by pulling API-based remote data such as revision history and audit logs, and collecting…
Spfx Release
pnp/docker-spfx
Automate SPFx version releases - branch, update files, commit, open PR, then tag after merge
Trader Memory Core
tradermonty/claude-trading-skills
Track investment theses across their lifecycle — from screening idea to closed position with postmortem.
Author Migration
nrwl/nx
Author or scope a first-party Nx migration. An agent skill from nrwl/nx.
Write Notes Like Deepseek
czm15053/write-notes-like-deepseek
A skill your agent uses when a change is non-trivial by DSH standards (behavior, architecture, cross-file contracts, process/tooling, testing strategy, or on-disk/wire/config formats), when choosing…
More from mohitagw15856/pm-claude-skills
All 1,348 skills in this repoCar Tco
mohitagw15856/pm-claude-skills
Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…
Cs Health Scorecard
mohitagw15856/pm-claude-skills
Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.
Exit Waterfall
mohitagw15856/pm-claude-skills
Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.
Feature Prioritisation
mohitagw15856/pm-claude-skills
Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.
Fire Number
mohitagw15856/pm-claude-skills
Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.
Freelance Rate
mohitagw15856/pm-claude-skills
Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.
Related
Works with
Categories
Questions about Migration Day Runbook
What does Migration Day Runbook do?
Move a team's files to a new platform without losing work or a week — the pre-migration freeze, the verified copy, the permissions remap, the cutover announcement, and the old-system read-only…. Migration Day Runbook is an agent skill from mohitagw15856/pm-claude-skills. Move a team's files to a new platform without losing work or a week — the pre-migration freeze, the verified copy, the permissions remap, the cutover announcement, and the old-system read-only afterlife.
When should I use Migration Day Runbook?
Migration Day Runbook fits situations like: asked were moving from Dropbox to Drive; migrate our files to SharePoint; plan the file migration day; how do we switch platforms safely.
How do I install Migration Day Runbook in Claude Code?
Run `npx skills add mohitagw15856/pm-claude-skills --skill migration-day-runbook -a claude-code`. Or copy the skill folder (skills/migration-day-runbook in mohitagw15856/pm-claude-skills) into .claude/skills/migration-day-runbook in your project. Claude Code loads it when a task matches its description.
How do I install Migration Day Runbook in Codex?
Run `npx skills add mohitagw15856/pm-claude-skills --skill migration-day-runbook -a codex`. Or copy the skill folder (skills/migration-day-runbook in mohitagw15856/pm-claude-skills) into .agents/skills/migration-day-runbook in your project. Codex loads it when a task matches its description.
Can I use Migration Day Runbook in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mohitagw15856/pm-claude-skills --skill migration-day-runbook -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/migration-day-runbook, .gemini/skills/migration-day-runbook, .github/skills/migration-day-runbook and .opencode/skills/migration-day-runbook in your project.
What does Migration Day Runbook need to run?
SKILL.md names no scripts, command-line tools or credentials: Migration Day Runbook is instructions for the agent only.
Does Migration Day Runbook access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Migration Day Runbook safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Migration Day Runbook use?
Migration Day Runbook is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Migration Day Runbook use?
About 1.5k tokens (SKILL.md is roughly 5.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Migration Day Runbook?
Skills that share tags, products or a category with Migration Day Runbook: Recipe Post Mortem Setup (googleworkspace/cli, 31k stars), Performing Cloud Storage Forensic Acquisition (mukul975/Anthropic-Cybersecurity-Skills, 34k stars), Spfx Release (pnp/docker-spfx, 134 stars) and Trader Memory Core (tradermonty/claude-trading-skills, 3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Migration Day Runbook?
mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,434 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 9, 2026.
Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.