Run a skill

Every MixShift skill runs the same two ways. Use whichever feels natural.

Ask in plain English

Describe what you want and name the brand where it matters:

• "Run the daily health check for [brand]."
• "Pull last month's Sales and Traffic report for [brand]."
• "Which search terms should we negate for [brand]?"

Claude picks the right skill and confirms before doing anything consequential.

Or invoke it directly

Each skill has a slash command in the form /mixshift-ai:mx-[skill]. Brand skills take the brand as an argument, for example:

• /mixshift-ai:mx-daily-health-check [brand]
• /mixshift-ai:mx-data-explore

The skill catalog lists every command.

What to expect

• Changes preview first. Any operation that would change something in your ad account shows you the exact change set and waits for your confirmation. If you decline, nothing is sent to Amazon.
• Big results become files. Large query results and report downloads save as CSV files with a short preview in chat, so your conversation stays readable and the full data is on disk.
• Slow pulls are normal for some sources. Amazon generates some reports asynchronously (AMC especially); the skill submits, keeps checking, and tells you when results are in.
• Some skills want brand context. The analytical tier reads your brand profile; run brand setup once per brand first.

Finding the right skill

Say "mixshift help" or run /mixshift-ai:mx-help for a guided capability map, grouped by what you are trying to get done. The same map lives in the skill catalog.

Related

• Skill catalog
• Set up a brand
• What the plugin can do