- name
Add or maintain a built-in BYOK media provider in the OpenMotion repository, including official API research, credentials, model discovery, generation adapters, editor configuration, provider referenc
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add nexu-io/openmotion --skill add-byok-provider -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add nexu-io/openmotion --skill add-byok-provider -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add nexu-io/openmotion --skill add-byok-provider -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add nexu-io/openmotion --skill add-byok-provider -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/nexu-io/openmotion/tree/HEAD/.agents/skills/add-byok-providerFrom the publisher
Use this repository-local contributor Skill to implement a provider through the existing openmotion_media_use Tool and Model Gateway. Read the checkout's AGENTS.md and follow its current development/PR rules. Paths below are relative to the repository root. This Skill stays in .agents/skills/; product guidance ships from root skills/.
Start with gateway behavior, then inspect the current callers and the closest existing adapter. Use Atlas for a shared image/video/audio prediction API, fal for returned queue URLs, WaveSpeed for authenticated discovery, and OpenDesign for a custom HTTPS gateway. Check current code instead of copying an entire provider or its assumptions.
Find and read the provider's official API/model documentation. Record source links and the date checked in its reference. Establish:
Implement only confirmed API behavior. Do not invent a model catalogue endpoint, account entitlement, unsupported modality, remote cancellation or refund. If documentation leaves a blocking ambiguity, explain the missing contract while continuing independent work.
Inspect these boundaries and update the ones the provider needs:
The public Tool already covers inspect/reference/models/generate/status/cancel. Reuse those actions; a supplier does not need its own MCP Tool or distributable Skill. Preserve the existing production routes and intentional UI visibility decisions. Tool and Skill lists come from their actual registries; do not introduce fixed quantity gates.
text, others prompt; the existing mode controls that mapping. Cloud speech additionally nests options. Check the wire body, not just the Tool arguments.apiJson, media validation and project-owned imports. Recognize their limits: current non-2xx handling omits raw provider bodies/headers, and local errors can omit task detail. Do not promise full provider diagnostics or infer a definitive cause from generic local wording.Create skills/openmotion-media/references/providers/<provider-id>.md and register it as described above. Read one existing document, such as Atlas, for the maintained shape; do not duplicate its supplier-specific facts.
Include key setup, authentication and model-list queries; openmotion_assets_use JSON templates for each supported modality; their exact HTTP endpoint/body mapping; polling/result retrieval; representative error codes with meaning, next action and retry boundaries; official source/model links and known integration limits. Distinguish Tool arguments from wire JSON, local job IDs from remote task IDs, and HTTP status from application/task codes. Mark unspecified behavior as unknown.
Keep real keys and internal/private source material out of the document. Put shell wire examples in this Skill's wire examples, not in the product reference, using environment placeholders only. Direct Agents through the Tools so the service owns credentials. Templates do not execute paid requests by themselves. Do not add this contributor Skill to packagedSkills, workflow resources or host installation lists.
Use deterministic fixtures to cover the new provider's real boundaries:
Adapt existing tests in tests/byok.test.ts, studio/src/motion/ModelSettings.test.tsx, tests/workflow.test.ts, tests/npm-package.test.ts and tests/byok-browser.mjs. Add assertions for observable behavior, not documentation wording. Ensure a new test file is included in the repository's explicit CI runner.
For runtime/Studio changes run npm run check, npm run typecheck:studio, npm run build:studio and affected deterministic/packaging checks under the pinned Node version. Use the shared browser-lock lane for real browser tests when available, or the exclusive isolated lane in tests/byok-browser.mjs; always use an isolated test project/data directory. Follow AGENTS.md when selecting narrower checks for documentation-only work.
Review docs/product/architecture.md and update it only if product behavior or boundaries changed. Report implemented modalities, references, actual checks, untested live-provider behavior and remaining limits. Run real paid generation only within the user's requested scope; fixture success is not account/billing or audiovisual acceptance. Commit/push/PR/merge/publication follow the current task authorization separately.
© 2026 Skills Rack.
---name: add-byok-providerdescription: Add or maintain a built-in BYOK media provider in the OpenMotion repository, including official API research…---# .agents/skills/add-byok-provider/SKILL.mdOverview
Add or maintain a built-in BYOK media provider in the OpenMotion repository, including official API research, credentials, model discovery, generation adapters, editor configuration, provider references and verification. Use for contributor requests to integrate a supplier; ordinary media generation uses the openmotion-media Skill.
FAQ
Download .agents/skills/add-byok-provider/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/nexu-io/openmotion.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.