Kubeshark Installer
kubeshark/kubeshark
Installs and configures Kubeshark on a Kubernetes cluster, choosing between the quick CLI path and a Helm install with custom values.
Plan the migration of an LLM feature from one model to another without breaking production.
Install Model Migration Plan
$ npx skills add mohitagw15856/pm-claude-skills --skill model-migration-plan -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitagw15856/pm-claude-skills model-migration-plan --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/model-migration-plan .claude/skills/model-migration-plan && 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 "model-migration-plan" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/model-migration-plan into .claude/skills/model-migration-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "model-migration-plan", 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/model-migration-planType 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 model-migration-plan -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitagw15856/pm-claude-skills model-migration-plan --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/model-migration-plan .agents/skills/model-migration-plan && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "model-migration-plan" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/model-migration-plan into .agents/skills/model-migration-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "model-migration-plan", 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 model-migration-plan -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitagw15856/pm-claude-skills model-migration-plan --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/model-migration-plan .cursor/skills/model-migration-plan && 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 "model-migration-plan" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/model-migration-plan into .cursor/skills/model-migration-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "model-migration-plan", 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/model-migration-plan--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 model-migration-plan -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitagw15856/pm-claude-skills model-migration-plan --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/model-migration-plan .gemini/skills/model-migration-plan && 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 "model-migration-plan" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/model-migration-plan into .gemini/skills/model-migration-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "model-migration-plan", 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 model-migration-planInstalls 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 model-migration-plan -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/model-migration-plan .github/skills/model-migration-plan && 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 "model-migration-plan" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/model-migration-plan into .github/skills/model-migration-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "model-migration-plan", 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 model-migration-plan -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 model-migration-plan --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/model-migration-plan .opencode/skills/model-migration-plan && 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 "model-migration-plan" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/model-migration-plan into .opencode/skills/model-migration-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "model-migration-plan", 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
model-migration-plan- GitHub stars
- 1.4k
- Token cost
- ~1.4k tokens
- SKILL.md length
- 690 words
- Files
- 1
- Skills in repo
- 1,348
- Repo updated
- First seen
- Licence
- MIT
At a glance
Plan the migration of an LLM feature from one model to another without breaking production.
- A model is being deprecated
- SKILL.md covers What This Skill Produces, Required Inputs, Migration Phases and Prompt Adaptation Notes, plus 5 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- A newer model looks better
What it does
Model Migration Plan is an agent skill from mohitagw15856/pm-claude-skills. Plan the migration of an LLM feature from one model to another without breaking production. Use when a model is being deprecated, a newer model looks better or cheaper, or when asked how to upgrade models safely, run shadow traffic, or set rollback criteria for a model change. Produces a phased migration plan with eval gates, shadow/canary stages, prompt-adaptation notes, and rollback triggers. For choosing which model in the first place use model-selection-advisor.
Its SKILL.md is about 1.4k 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 Deployment. 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
- A model is being deprecated
- A newer model looks better
- Asked how to upgrade models safely
- Run shadow traffic
Example prompts
- “/model-migration-plan”
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
Model Migration Plan loads about 1.4k tokens when it runs. Until then it costs about 123 tokens; SKILL.md has 690 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). 690 words, ~1,350 tokens.
Download SKILL.mdSave it as
.claude/skills/model-migration-plan/SKILL.md (or your agent's skills folder).- name
- model-migration-plan
- description
- Plan the migration of an LLM feature from one model to another without breaking production. Use when a model is being deprecated, a newer model looks better or cheaper, or when asked how to upgrade models safely, run shadow traffic, or set rollback criteria for a model change. Produces a phased migration plan with eval gates, shadow/canary stages, prompt-adaptation notes, and rollback triggers. For choosing which model in the first place use model-selection-advisor.
Model Migration Plan Skill
A model swap changes every output of your feature at once. This skill plans the migration like the risky deploy it is: eval first, shadow second, canary third — with numbers, not vibes, deciding each promotion.
What This Skill Produces
- A phased migration plan (eval → shadow → canary → full) with promotion criteria per phase
- Prompt adaptation notes — what typically shifts between models and what to re-tune
- Rollback triggers and the mechanics of rolling back fast
- A cost/latency delta forecast for the new model
Required Inputs
Ask for (if not already provided):
- Current and target model (and why: deprecation, quality, cost, latency)
- The feature's traffic and blast radius — requests/day, who sees the output, what a bad output costs
- Existing evals — a regression suite (see
prompt-regression-suite) or at minimum golden examples; if none exist, phase 0 is building one - The deadline, if the migration is forced by a deprecation date
Migration Phases
Phase 0 — Baseline. Freeze a regression suite against the current model. Without a baseline, "the new model is fine" is unfalsifiable. Record current cost, latency (p50/p95), and quality scores.
Phase 1 — Offline eval. Run the suite against the target model with the prompt as-is, then with adapted prompts. Promotion criteria: pass rate ≥ baseline, no canary failures, cost/latency within budget. Expect to iterate here — most "model regressions" are prompt-fit issues.
Phase 2 — Shadow. Mirror a sample of real traffic to the new model; log, never serve. Compare distributions: refusal rate, output length, format-violation rate, judge scores on a sample. Duration: long enough to cover weekly traffic patterns.
Phase 3 — Canary. Serve the new model to [1-5]% of traffic behind a flag, tagged in analytics. Watch the same metrics plus user-visible signals (regenerate rate, thumbs-down, support tickets). Widen in steps; each step has the same promotion criteria.
Phase 4 — Full cutover + cleanup. 100% traffic, old model kept warm behind the flag for [period], then removed. Update model pins everywhere (including the eval judge if it referenced the old model), and re-baseline the regression suite on the new model.
Prompt Adaptation Notes
Between model generations, re-check: instruction-following strictness (newer models often follow the letter, exposing sloppy prompts), format compliance (JSON/markdown habits differ), verbosity defaults, refusal boundaries, tool-calling style, and system-prompt sensitivity. Adapt the prompt per model rather than writing to the lowest common denominator — keep per-model prompt versions if both run simultaneously.
Show full SKILL.md (299 more words)Show less
Rollback
- Triggers (numbers, set in advance): canary quality below baseline by [X], refusal/format-violation rate above [Y], p95 latency above [Z], or any safety incident.
- Mechanics: the model is a config flag, not a code deploy — rollback is a flag flip taking effect in [minutes]. State who can flip it and how it's tested before the canary starts.
Output Format
Model Migration Plan: [feature] — [current model] → [target model]
Why now: [driver + deadline]. Blast radius: [traffic, audience, cost of a bad output].
| Phase | Gate to pass | Duration | Owner |
|---|---|---|---|
| 0 Baseline | suite frozen; cost/latency recorded | ||
| 1 Offline eval | [criteria] | ||
| 2 Shadow | [criteria] | ||
| 3 Canary [x]% → [y]% | [criteria] | ||
| 4 Cutover + cleanup | [criteria] |
Prompt adaptations found/expected: [list]
Rollback: triggers [numbers]; mechanism [flag]; owner [who].
Cost/latency forecast: [current] → [projected], at [traffic].
Quality Checks
- Every phase promotion criterion is a number against the recorded baseline
- Shadow phase compares distributions, not anecdotes ("outputs look good" is not a gate)
- Rollback is a config flip with a named owner, tested before canary
- The plan re-baselines the regression suite after cutover — the new model becomes the new normal
- Deprecation deadlines leave slack for at least one failed phase-1 iteration
Anti-Patterns
- Do not skip shadow because offline evals passed — real traffic finds what golden sets miss
- Do not migrate the feature and the prompt redesign in one change — you won't know which moved the metrics
- Do not compare models with an unpinned judge, or a judge that is the target model grading itself
- Do not leave the old model path in code indefinitely "just in case" — set the removal date in the plan
- Do not treat a cheaper model as free savings without re-checking quality at the tails, not just the mean
Example Trigger Phrases
- "How to upgrade models safely?"
- "Run shadow traffic."
- "Set rollback criteria for a model change."
© 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/model-migration-plan of mohitagw15856/pm-claude-skills.
Open the folder on GitHubat commit 1cbf1f0
Compare with similar skills
Model Migration Plan 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 |
|---|---|---|---|---|---|---|
| Model Migration Plan this skillmohitagw15856/pm-claude-skills | 1.4k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Kubeshark Installerkubeshark/kubeshark | 12k | — | ~3.6k | Automated safety check: Notes | Apache-2.0 | |
| GreptimeDB Dev Docker ImageGreptimeTeam/greptimedb | 6.7k | — | ~4k | Automated safety check: Notes | Apache-2.0 | |
| KubeSphere ServiceMesh Managerkubesphere/kubesphere | 17k | — | ~2.4k | Automated safety check: Pass | Custom licence | |
| Vercelremotion-dev/remotion | 63k | — | ~1.2k | Automated safety check: Pass | Custom licence | |
| AWS Cdk Developmentzxkane/aws-skills | 367 | 2 repos | ~2.5k | Automated safety check: Pass | MIT |
Similar skills
GreptimeDB Dev Docker Image
GreptimeTeam/greptimedb
Packages a locally built GreptimeDB debug binary into a development-only Docker image for local-cluster testing, with an optional push to a dev registry.
KubeSphere ServiceMesh Manager
kubesphere/kubesphere
Installs, checks and troubleshoots the KubeSphere ServiceMesh extension (Istio, Kiali, Jaeger), including grayscale release, sidecar injection, topology and tracing issues.
- Official
Vercel
remotion-dev/remotion
Set up a Codex monitor for Vercel deployments and preview URLs.
AWS Cdk Development
zxkane/aws-skills
AWS Cloud Development Kit (CDK) expert for building cloud infrastructure with TypeScript/Python.
Senior DevOps Toolkit
maslennikov-ig/claude-code-orchestrator-kit
Comprehensive DevOps skill for CI/CD, infrastructure automation, containerization, and cloud platforms (AWS, GCP, Azure). Includes pipeline setup…
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
Categories
Questions about Model Migration Plan
What does Model Migration Plan do?
Plan the migration of an LLM feature from one model to another without breaking production. Model Migration Plan is an agent skill from mohitagw15856/pm-claude-skills. Plan the migration of an LLM feature from one model to another without breaking production.
When should I use Model Migration Plan?
Model Migration Plan fits situations like: A model is being deprecated; A newer model looks better; asked how to upgrade models safely; run shadow traffic.
How do I install Model Migration Plan in Claude Code?
Run `npx skills add mohitagw15856/pm-claude-skills --skill model-migration-plan -a claude-code`. Or copy the skill folder (skills/model-migration-plan in mohitagw15856/pm-claude-skills) into .claude/skills/model-migration-plan in your project. Claude Code loads it when a task matches its description.
How do I install Model Migration Plan in Codex?
Run `npx skills add mohitagw15856/pm-claude-skills --skill model-migration-plan -a codex`. Or copy the skill folder (skills/model-migration-plan in mohitagw15856/pm-claude-skills) into .agents/skills/model-migration-plan in your project. Codex loads it when a task matches its description.
Can I use Model Migration Plan 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 model-migration-plan -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/model-migration-plan, .gemini/skills/model-migration-plan, .github/skills/model-migration-plan and .opencode/skills/model-migration-plan in your project.
What does Model Migration Plan need to run?
SKILL.md names no scripts, command-line tools or credentials: Model Migration Plan is instructions for the agent only.
Does Model Migration Plan 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 Model Migration Plan 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 Model Migration Plan use?
Model Migration Plan 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 Model Migration Plan use?
About 1.4k tokens (SKILL.md is roughly 5.4k 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 Model Migration Plan?
Skills that share tags, products or a category with Model Migration Plan: Kubeshark Installer (kubeshark/kubeshark, 12k stars), GreptimeDB Dev Docker Image (GreptimeTeam/greptimedb, 6.7k stars), KubeSphere ServiceMesh Manager (kubesphere/kubesphere, 17k stars) and Vercel (remotion-dev/remotion, 63k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Model Migration Plan?
mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,433 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 8, 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.