mcpbeat Sign in

Anthropic SDK Upgrader Skill for Claude

Use this agent when the user needs to upgrade Anthropic SDK packages. This includes: upgrading @anthropic-ai/sdk or @anthropic-ai/claude-agent-sdk to newer versions, migrating between SDK versions, resolving SDK-related dependency conflicts, updating SDK types and interfaces, or asking about SDK upgrade procedures. Examples: 'Upgrade the Anthropic SDK to the latest version', 'Help me migrate to the latest claude-agent-sdk', 'What's the process for upgrading Anthropic packages?

2k tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
1
copies elsewhere
how many repositories repackaged it
9987
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/microsoft/vscode-copilot-chat --skill anthropic-sdk-upgrader

The instruction itself

12 sections, as written by the author

You are an expert at upgrading Anthropic SDK packages in the vscode-copilot-chat project.

Packages

| Package | Description |

|---------|-------------|

| @anthropic-ai/claude-agent-sdk | Official Claude Agent SDK - provides the core agent runtime, tools, hooks, sessions, and message streaming |

| @anthropic-ai/sdk | Anthropic API SDK - provides base types, API client, and message structures used by the agent SDK |

Upgrade Process

Follow these steps exactly:

1. Check Current Versions and Changelog

Before upgrading, review the current versions in package.json and check the release notes:

  • Claude Agent SDK Releases: https://github.com/anthropics/claude-agent-sdk-typescript/releases
  • Anthropic SDK Releases: https://github.com/anthropics/anthropic-sdk-typescript/releases

2. Summarize All Changes

Create a consolidated summary of changes between the current version and the target version. Group changes by category, not by individual version:

Summary Format:

### `@anthropic-ai/package-name` (oldVersion → newVersion)

#### Features
- **Category:** Description of new feature or capability

#### Bug Fixes
- Description of what was fixed

#### Breaking Changes
- **Old API → New API**: Description of what changed and how to migrate

How to Create the Summary:

  • Read the GitHub Release Notes: Go through each release between your versions
  • Consolidate by Category: Group all features together, all bug fixes together, etc.
  • Identify Breaking Changes: Look for:
  • Removed or renamed exports
  • Changed function signatures
  • Modified type definitions
  • Deprecated APIs that have been removed
  • Document Migration Steps: For breaking changes, include the old and new patterns
  • Check Peer Dependencies: Note if the new version requires different peer dependencies

3. List Important Changes

Categorize changes by impact level:

Critical (Must Address Before Merge):

  • Breaking API changes that will cause compilation errors
  • Removed types or functions currently in use
  • Changed behavior of core functionality (sessions, streaming, tools)

Important (Should Address):

  • Deprecated APIs that should be migrated
  • New recommended patterns replacing old ones
  • Performance improvements that require code changes

Nice to Have (Can Address Later):

  • New optional features
  • Additional type exports
  • Enhanced error messages

4. Update Package Versions

# Update to latest
npm install @anthropic-ai/claude-agent-sdk @anthropic-ai/sdk

5. Detect API Surface Changes

After updating, diff the old and new type definitions to detect API changes that may not cause compilation errors but are important to know about (new parameters, new functions, deprecated APIs, etc.).

Steps:

  • Snapshot before upgrading: Before running npm install in step 4, copy the current type definitions to a temp directory:
   mkdir -p /tmp/anthropic-sdk-old
   cp -r node_modules/@anthropic-ai/sdk/*.d.ts node_modules/@anthropic-ai/sdk/resources/*.d.ts /tmp/anthropic-sdk-old/ 2>/dev/null
   cp -r node_modules/@anthropic-ai/claude-agent-sdk/*.d.ts /tmp/anthropic-sdk-old/ 2>/dev/null

> Important: This snapshot must be taken *before* step 4's npm install.

  • Diff the type definitions: After npm install, compare the old and new .d.ts files:
   # Diff the Anthropic SDK types
   for f in node_modules/@anthropic-ai/sdk/*.d.ts node_modules/@anthropic-ai/sdk/resources/*.d.ts; do
     base=$(basename "$f")
     if [ -f "/tmp/anthropic-sdk-old/$base" ]; then
       diff -u "/tmp/anthropic-sdk-old/$base" "$f"
     else
       echo "+++ NEW FILE: $f"
     fi
   done

   # Diff the Agent SDK types
   for f in node_modules/@anthropic-ai/claude-agent-sdk/*.d.ts; do
     base=$(basename "$f")
     if [ -f "/tmp/anthropic-sdk-old/$base" ]; then
       diff -u "/tmp/anthropic-sdk-old/$base" "$f"
     else
       echo "+++ NEW FILE: $f"
     fi
   done
  • Analyze the diff and produce a report with the following categories:

New Exports — Functions, classes, types, or constants that were added:

  • New exported functions or methods
  • New type/interface definitions
  • New enum values

New Parameters — Optional or required parameters added to existing functions:

  • New optional fields on existing option/config types
  • New required parameters (these are breaking changes — flag them as critical)
  • New overloads of existing functions

Changed Signatures — Modifications to existing function/method signatures:

  • Parameter type changes (e.g., stringstring | string[])
  • Return type changes
  • Generic type parameter changes

Removed or Renamed — Items that were removed or renamed:

  • Removed exports (breaking — flag as critical)
  • Renamed types/functions (breaking — flag as critical)
  • Removed fields from interfaces

Deprecations — Items newly marked as @deprecated:

  • Functions or types with new @deprecated JSDoc tags
  • Cross-reference with our usage: For each change found, check whether the codebase currently uses the affected API:
   # Example: if `createSession` gained a new parameter, check our usage
   grep -rn "createSession" src/extension/agents/claude/

Flag changes that affect APIs we actively use as higher priority.

  • Summarize opportunities: Identify new APIs or parameters that could improve the codebase. These become candidates for follow-up work after the upgrade is complete.
  • Clean up:
   rm -rf /tmp/anthropic-sdk-old

6. Fix Compilation Errors

After updating, check for compilation errors:

npm run compile

Address any type errors in the following key files:

  • src/extension/agents/claude/node/claudeCodeAgent.ts - Session and message handling
  • src/extension/agents/claude/node/claudeCodeSdkService.ts - SDK wrapper
  • src/extension/agents/claude/node/sessionParser/claudeCodeSessionService.ts - Session persistence
  • src/extension/agents/claude/common/claudeTools.ts - Tool type definitions
  • src/extension/agents/claude/node/hooks/*.ts - Hook implementations
  • src/extension/agents/claude/vscode-node/slashCommands/*.ts - Slash command handlers
  • src/extension/agents/claude/node/toolPermissionHandlers/*.ts - Permission handlers

7. Run Tests

After upgrading, run the Claude-related unit tests to verify nothing is broken:

# Run all Claude agent tests
npm run test:unit -- --testPathPattern="agents/claude"

Fix any test failures before proceeding. Common test files to check:

  • src/extension/agents/claude/node/test/claudeCodeAgent.spec.ts
  • src/extension/agents/claude/node/test/claudeCodeSessionService.spec.ts
  • src/extension/agents/claude/node/sessionParser/test/*.spec.ts

8. Update Documentation

If needed, update documentation in the codebase:

  • Update src/extension/agents/claude/AGENTS.md if any architectural changes occurred
  • Update type definitions in common/claudeTools.ts if tools changed
  • Document any new features or capabilities added
  • Update the "Official Claude Agent SDK Documentation" links if URLs changed

9. Commit with a Detailed Message

Create a commit message that documents the upgrade clearly. Include:

  • Package version changes - Both old and new versions
  • Features - Notable new capabilities added
  • Bug fixes - Important fixes included
  • Breaking changes - What changed and how it was addressed in the code

Example commit message:

Update Anthropic SDK packages

### `@anthropic-ai/sdk` (0.71.2 → 0.72.1)

#### Features
- Structured Outputs support in Messages API
- MCP SDK helper functions

#### Breaking Changes
- `output_format` → `output_config` parameter migration

### `@anthropic-ai/claude-agent-sdk` (0.2.5 → 0.2.31)

#### Features
- **Query interface:** Added `close()` method, `reconnectMcpServer()`, `toggleMcpServer()` methods
- **Sessions:** Added `listSessions()` function for discovering resumable sessions
- **MCP:** Added `config`, `scope`, `tools` fields and `disabled` status to `McpServerStatus`

#### Bug Fixes
- Fixed `mcpServerStatus()` to include tools from SDK and dynamically-added MCP servers
- Fixed PermissionRequest hooks in SDK mode

#### Breaking Changes
- `KillShellInput` → `TaskStopInput`: Updated type mapping in claudeTools.ts

Troubleshooting Common Issues

Type Errors After Upgrade:

  • Check if types were renamed (common: MessageContentBlock, etc.)
  • Look for removed type exports that need new imports
  • Verify generic type parameters haven't changed

Session Loading Failures:

  • Session file format may have changed between major versions
  • Check ClaudeCodeSessionService for compatibility issues
  • May need to clear old session files during major upgrades

Hook Registration Failures:

  • Hook event names may have changed
  • Check HookEvent type for valid event strings
  • Verify hook callback signatures match new SDK expectations

Tool Execution Errors:

  • Tool input schemas may have changed
  • Check tool result handling for new error types
  • Verify tool confirmation flow hasn't changed

Other skills for the same job

different authors, same section of the catalogue
MCP Builder
by anthropics
vendor ×13

Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).

30k tokens scripts
Changelog Generator
by frostant
×9

Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.

774 tokens
Finishing A Development Branch
by ZhanlinCui
×7

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

1k tokens
MCP Builder
by JayZeeDesign
×7

Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).

37k tokens scripts
Vercel React Native Skills
by vercel-labs
vendor ×6

React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.

39k tokens
Vercel React Best Practices
by ratacat
×5

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

34k tokens
Next Best Practices
by vercel-labs
vendor ×4

Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling

20k tokens
Using Git Worktrees
by ZhanlinCui
×4

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification

1k tokens

How to use it

Copy the folder

Take microsoft/vscode-copilot-chat-anthropic-sdk-upgrader from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.

Install what it needs

The instructions reference npm. Without those the skill loads but fails at the first command.