Complete AI Training
Sign inGet started

Skill · Business

Claude opus 4 5 migration

Migrates codebases from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5 by updating model strings, removing the context-1m beta header, and adding the effort parameter. Use when the user asks to migrate, upgrade, or switch models to Opus 4.5.

Complete AI SkillsLicense: MITAdded Sep 29, 2026
SalesHuman ResourcesFinance & AccountingProduct Management
Use it in my AI View on TemplatesGrokBot

How to use it

  1. Start your plan and connect your AI once
  2. Ask for the task in your own words, or say it directly:
Use the Claude opus 4 5 migration skill to help me with this.

Without a connection: copy the SKILL.md below into your AI's project instructions.

SKILL.md

Claude Opus 4.5 Migration

This skill helps developers move an existing codebase from Claude Sonnet 4.0, Sonnet 4.5, or Opus 4.1 to Opus 4.5. It covers model string replacement across Anthropic API, AWS Bedrock, Google Vertex AI, and Azure AI Foundry, beta header cleanup, effort parameter addition, and an optional prompt adjustment step. It is for users who want a controlled, reviewable migration rather than a blind find-and-replace.

When to use

  • The user asks to migrate, upgrade, or switch their code to Opus 4.5.
  • The user is moving off Sonnet 4.0, Sonnet 4.5, or Opus 4.1.
  • The user wants model strings, beta headers, or the effort parameter updated for Opus 4.5.
  • The user reports a specific prompt behavior issue after migrating and asks for help.

Workflows

Model string migration

Inputs: The codebase or files to migrate, the source model(s) being migrated from, and the platform(s) in use.

  1. Search the codebase for model strings matching Sonnet 4.0, Sonnet 4.5, or Opus 4.1.
  2. Cover all platforms present: Anthropic API, AWS Bedrock, Google Vertex AI, and Azure AI Foundry.
  3. Replace each matched string with the corresponding Opus 4.5 model string.
  4. Leave all other model strings unchanged.
  5. Do not touch Haiku 4.5 strings or any model not in the source table.

    6. Check: Every Sonnet 4.0, Sonnet 4.5, and Opus 4.1 string is replaced; no Haiku 4.5 or out-of-scope strings were changed. Output: A list of files modified and the exact string replacements made.

Beta header cleanup

Inputs: The API call sites in the migrated files.

  1. Find the context-1m-2025-08-07 beta header in API calls.
  2. Remove it.
  3. Replace it with a comment noting that 1M context is not yet supported with Opus 4.5.
  4. Do not modify any other beta headers.

    5. Check: The context-1m-2025-08-07 header is gone and replaced by the comment; all other beta headers are untouched. Output: A list of files where the header was removed and the comment added.

Effort parameter addition

Inputs: The API calls being migrated.

  1. Add the effort parameter set to 'high' to every API call being migrated.
  2. If the user asks about configuring the effort parameter further, refer them to the effort reference and ask for their preference.

    3. Check: Every migrated API call has the effort parameter set to 'high'. Output: A list of files where the effort parameter was added.

Prompt adjustment (on request only)

Inputs: The specific issue the user reports and the relevant prompt-snippets reference.

  1. Do not apply any prompt adjustments by default.
  2. If the user reports a specific issue—tool overtriggering, over-engineering, code exploration reluctance, frontend design quality, or thinking sensitivity—ask clarifying questions first.
  3. Apply the relevant snippet from the prompt-snippets reference.
  4. Integrate it thoughtfully into existing prompts using XML tags and matching the existing style.

    5. Check: The snippet addresses the reported issue and matches the existing prompt style. Output: The proposed prompt edits with the integrated snippet.

Change summary

Inputs: The completed migration work.

  1. After completing all migrations, produce a clear summary of every change made.
  2. Include which files were modified, which model strings were replaced, which beta headers were removed, and which effort parameters were added.
  3. If no changes were needed, say nothing.

    4. Check: The summary covers all four change categories and matches the actual edits. Output: A structured summary of files modified, model strings replaced, beta headers removed, and effort parameters added.

Tools and data

  • Use the effort reference when the user asks about configuring the effort parameter further.
  • Use the prompt-snippets reference when applying a requested prompt adjustment.

Guardrails

  • Never apply prompt adjustments unless the user explicitly reports an issue and requests help.
  • Never migrate Haiku 4.5 model strings or any model not listed in the source table.
  • Never make changes outside the scope of model string updates, beta header removal, and effort parameter addition without user confirmation.
  • Draft all changes as proposed edits—do not modify files directly without user approval.

Getting started

Ask the user to share their codebase or provide the files that need migration. Then ask which source model(s) they are migrating from and which platform(s) they use.

Credits

Adapted from an open-source original (MIT): https://www.aitmpl.com/component/skills/development/claude-opus-4-5-migration

More business skills

All business skills

Prompts that go with Claude opus 4 5 migration

All prompts