What problem does it solve? Adding a new video-generation provider to the OpenRouter platform requires touching many coordinated pieces—adapter code, enums, pricing SKUs, factory registration, and tests—and missing any one of them produces silent routing or billing failures. This Skill guides the implementation of a complete provider adapter from a finished research note. ## Core Features & Use Cases - Adapter Implementation: Extends BaseVideoGenerationAdapter with getUrl, transformRequest, transformResponse, getVideoDuration, and getEstimatedSKUItems, using Zod to validate upstream submit, poll, terminal, and artifact responses. - Job Lifecycle & Capability Mapping: Classifies pending/running/completed/failed/cancelled states correctly and extends serving enums so staged supported_video_parameters stay schema-valid. - Pricing and Registration: Defines per-second/per-video SKU units and registers the strategy, adapter enum, factory entry, provider mapping, and endpoint pricing override. - Use Case: After completing a research note at docs/video-research/<provider>.md, use this Skill to implement the full adapter, wire pricing, and add tests covering submit, poll states, artifact fetch, and SKU calculation. ## Quick Start Implement a new video-generation provider adapter from the completed research note in docs/video-research, including pricing registration and tests.