Agent skill · software engineering · jeremylongshore
anth-migration-deep-dive
Migrate to Claude API from OpenAI, Gemini, or other LLM providers.
Why this skill is useful
Provides detailed migration scripts and API mapping for switching to Claude from other LLMs, which the AI wouldn't generate on its own.
What it needs
Requires anthropic, openai installed locally. Requires anthropic, openai account access. About 4k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Anthropic Migration Deep Dive Overview Migration strategies for switching to Claude from OpenAI, Google, or other LLM providers, including API mapping, prompt translation, and multi-provider abstraction. OpenAI to Anthropic API Mapping OpenAI Anthropic Notes -------- ----------- ------- openai.ChatCompletion.create() anthropic.messages.create() Different response shape model: "gpt-4" model: "claude-sonnet-4-20250514" Different model IDs messages: [{role, content}] messages: [{role, content}] Same format functions / tools tools Similar but different schema key names functioncall toolchoice Different naming response.choices[0].message.content response.content[0].text Different access path stream: true → yields chunks stream: true → SSE events Different event format System message in messages[] system parameter (separate) Claude separates system prompt n (multiple completions) Not supported Use multiple requests logprobs Not supported N/A Side-by-Side Code Comparison Tool Use Migration Multi-Provider Abstraction Migration Checklist [ ] Map model names (GPT-4 → Claude Sonnet, GPT-3.5 → Claude Haiku) [ ] Move system prompts from messages[] to system parameter [ ] Update response access path (.choices[0].message.content → .content[0].text) [ ] Make maxtokens explicit (required in Anthropic, optional in OpenAI) [ ] Update tool definitions to Anthropic format [ ] Test prompt behavior (Claude may respond differently to same prompts) [ ] Update error handling for Anthropic error types Prerequisites Inventory provider models, prompts, tools, response consumers, data flows, budgets, and retention rules. Obtain owner approval for the target model/workspace and rollback window. Define a provider-neutral contract with explicit fields for model, token budget, stop reason, tool calls, errors, usage, and correlation ID; keep provider-specific details behind the adapter. Prepare representative synthetic fixtures and a no-op tool registry in a sandbox. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/anth-migration-deep-dive