What problem does it solve?
Migrating agent functionality from the legacy @openrouter/sdk package to the standalone @openrouter/agent package requires updating dozens of import paths, package references, and type imports, which is time-consuming and prone to manual errors for TypeScript developers.
Core Features & Use Cases
- Complete Import Mapping: Provides exact before/after import paths for all agent-related exports including callModel, tool(), stop conditions, format converters, and type definitions.
- Mixed Project Support: Includes guidance for codebases that use both @openrouter/sdk for non-agent features (model listing, credits, OAuth) and @openrouter/agent for agent functionality.
- New Feature Coverage: Documents agent-only capabilities like shared context schemas, tool approval flows, and turn lifecycle callbacks that are not available in the legacy SDK.
Use case: A development team maintaining an OpenRouter-powered agent in TypeScript can use this skill to quickly update their codebase after the agent functionality was split into a separate package, avoiding broken imports and missing features.
Quick Start
Use this skill to update all your @openrouter/sdk agent-related imports and package references to the new @openrouter/agent package.