Choose xplaai Codex commerce skills by the result you need

xplaai Codex commerce skills are packaged workflows for Codex, with separate WorkBuddy packages for supported workflows. Each Skill defines the source material it needs, the steps the Agent coordinates, the local deliverables it creates and the xplaai API calls used during execution. Compare Skills by input and deliverable first, then choose the package and access flow for your Agent.

Start with a public case and an input/output comparison. Then choose the package for your Agent.

A Skill coordinates work beyond one API call

An API endpoint performs a specific task: generate an image, create a video task, produce speech or retrieve product data.

A Commerce Skill coordinates a repeatable workflow around those calls. Depending on the Skill, that can include:

• checking source files and required tools;
• organizing product or research inputs;
• drafting a plan or storyboard;
• reporting the expected task count before paid execution;
• generating media through xplaai APIs;
• assembling local outputs for review and editing;
• recording what completed and what still needs attention.

Use the xplaai API when you are building your own orchestration. Use a Commerce Skill when you want Codex or WorkBuddy to follow a packaged process inside your project.

Compare the current Commerce Skills

The detail page is the source of truth for current access, package availability and exact input requirements.

Choose by deliverable, not by model name

Product research

Choose TikTok Shop Product Research when the result should be a structured research board rather than media. The workflow can organize product links, images, market fields and a snapshot for review. A first snapshot is not automatically a trend.

Several product-video candidates

Choose Batch Commerce Video when you want to test several vertical creative directions from product material. The workflow separates sample approval and budget review from a larger queued run.

A pet-led short video

Choose Pet Video Auto Edit when the input combines pet copy and source assets and the result should include narration, storyboard continuity and a completed edit.

An illustrated explainer

Choose Dog Explainer Animation for Chinese educational narration and illustrated dog scenes. Choose Daoist Golden-Line Commerce Video when Chinese Daoist copy should become a black-and-gold narrated MP4 with editable subtitle and production assets.

English affiliate content

Choose the English Affiliate Video Skill when you have a product, English selling points and approved reference material and need an original vertical video plus editable project assets for TikTok, Reels or Shorts.

Review the public case before choosing a package

xplaai separates public proof from private distribution:

• case images and videos can be public so users can review the actual format;
• Codex and WorkBuddy packages are delivered through controlled download flows;
• member packages remain behind membership checks;
• a public media URL is not a ZIP download URL;
• copying a hidden button or page link does not replace server-side access validation.

This boundary lets a prospective user inspect the workflow without exposing private packages.

Codex and WorkBuddy use separate packages

Each supported Agent receives its own package. Do not assume that renaming one ZIP makes it valid for the other environment.

On a Skill detail page:

1. choose Codex or WorkBuddy;
2. download the package for that Agent;
3. give the ZIP to the Agent for local installation;
4. run the Skill's environment or doctor check;
5. configure the xplaai key locally;
6. run a dry-run or plan before approving paid API calls.

For Codex, follow the Codex Skill installation guide.

Keep secrets and generated files local

An xplaai API key should not be stored in a ZIP, prompt transcript, screenshot or public repository. Configure it locally using the selected Skill's instructions.

Generated files remain in the local project or the connected destination defined by the workflow. Review them before publishing. A Commerce Skill can prepare editable deliverables; it does not remove the need for brand, rights, claims or platform-policy checks.

Confirm work before paid execution

The first run should separate planning from execution:

1. ask the Agent to run the environment check;
2. provide the source material;
3. request a dry-run or execution plan;
4. review the expected image, speech, video or data-task count;
5. approve paid calls explicitly;
6. if a task fails, resume only the failed step where the Skill supports it.

Installing a Skill and using xplaai APIs are separate parts of the workflow. API usage follows the account and live product terms shown by xplaai.

Frequently asked questions

What is an xplaai Commerce Skill?

It is a packaged workflow for Codex or WorkBuddy that coordinates defined inputs, xplaai API calls and local deliverables.

How is a Skill different from an API?

An API performs an individual operation. A Skill coordinates several operations, checks and deliverables around a repeatable task.

Do the same ZIP files work in Codex and WorkBuddy?

Use the package made for your Agent. xplaai publishes separate Codex and WorkBuddy ZIPs for supported Skills.

Where do generated files go?

The workflow keeps results in the local project or a connected destination described by that Skill, so the user can review and edit them.

Are public cases the same as member downloads?

No. Public cases demonstrate the output format. Private member packages stay behind authenticated access controls.

Does installing a Skill include API usage?

Skill access and xplaai API usage are separate. Check the live Skill detail page and your account before approving execution.

Browse real Skill cases

Compare the input, output and public case for each workflow. When you have chosen one, install it in Codex and run a dry-run before the first paid task.