Domains
Forms
Mechanism
Breaks down how the skill works and what it produces, so you can quickly judge whether it fits your scenario and value.
When the user wants to update their codebase, prompts, or API calls from Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5. Also when user reports Opus 4.5 behavioral issues after migration.
Codebase and prompts migrated to Opus 4.5 with correct model strings and optional prompt tuning; user gets a clear change summary.
Use Cases
A team built an internal tool calling Sonnet 4.0 via Anthropic API. They want to adopt Opus 4.5 for better quality. Using this skill, they search the repo, replace model strings with claude-opus-4-5-20251101, drop the 1M context beta header, and add effort high. The skill summarizes changes, saving hours of manual find-replace and preventing invalid config.
After migrating to Opus 4.5, a developer finds the model creates too many files and triggers tools excessively. They use this skill to apply prompt adjustments: softening CRITICAL/MUST language and adding over-engineering prevention snippets from references. This resolves unwanted behavior without reverting the model upgrade.
Skill Relationships
Dependency relationships read as "the upper tier points to the lower tier." The current Skill sits in the middle tier — above are Skills that depend on it, below are Skills it depends on.
Tier 1 · These Skills Use Me
Tier 2 · Current Skill
Tier 3 · I Use These Skills
Browse this skill's relationships within its skillset. Click a node to switch the side panel; use the search box to jump to any skill.
Skill File
