Issue #3: Try this this week: mx-brand-context
The account knowledge that makes every skill brand-aware. Plus what we shipped this week.
Third issue. Same shape as the last two: one skill you can activate today, the things we shipped this week, one question we would like you to answer.
Try this this week: mx-brand-context
The problem. Every skill you run is only as sharp as what it knows about the account. A new brand is a cold start. The things that actually explain the numbers, the promos, the stockouts, the launches, the sub-brands, the ACOS targets, the brand terms you never want read as generic search, usually live in one person's head or one analyst's spreadsheet. When that person is out, the account loses its memory. When a skill runs without it, a planned promo reads as a problem.
And it compounds across a book of business. Every account you onboard starts blind, and every handoff between teammates drops context on the floor. The fix is not another dashboard. It is giving the tools the same brand knowledge you carry in your head.
The solution. mx-brand-context builds that knowledge once, as a structured brand context: the sub-brands and item groups, the ACOS targets and where they came from, the brand terms, and the structural events like promos, stockouts, and launches. Every other skill then reads the same brand truth, so runaway-spend-check, the daily health check, and the monthly report all judge the account against what you know about it, not a generic baseline.
Try this: open Claude with the MixShift plugin and say:
"set up brand context for <brand>"
You will get a guided walkthrough. It pulls the account's history, asks you the handful of things only you know, and writes it all into a brand context the whole toolset can use. Do it once per account. Everything downstream gets sharper for it.
One source of truth, any surface. Because the context lives with the account and not in your head, it carries across sessions and across managers. Everyone on the team works from the same brand truth, pointed at the same goals, whether they are in MixShift 2.0, their own app, an MCP client in any LLM, or the Claude plugin.
This week in MixShift
What we shipped this week, from the 2026-08-08 release. See the full notes at mixshift.ai/releases.
1. Your brand events now reach the whole team automatically
The structural events you record during brand setup, the promos, stockouts, launches, and migrations, used to live only on the machine where you entered them. They were invisible to reporting and to teammates. Now they publish to your org's brand timeline on their own: after you edit context, before a skill reads it, and on demand when you run a sync. Publishing never double-records, and an event with no start date is marked as recorded when you learned it, so a reader can tell when you found out from when it happened.
Now you can: enter a promo or a stockout once and have every teammate's skills see it, instead of each person keeping private notes that never line up.
2. Brand context now syncs both directions
Before a skill reads a brand, MixShift already pulled your team's newer copy. Now it also sends your newer local changes back, on every write, including the first time a brand is shared. Nothing is overwritten silently. If the same doc was edited in two places, it is flagged as a conflict for you to resolve. Every automatic share prints a one-line notice so you always know when something left your machine, and you can switch back to manual sharing if you prefer.
Now you can: stop emailing context files around. Edit a brand on your laptop and your teammate's next skill run already has your change.
3. Brand events fit whatever actually happened
Events no longer have to fit a fixed list. Three new types cover the cases that kept falling through: off-Amazon media programs, expected catalog rotation like seasonal flavors or planned discontinuations, and an explicit other type for anything else, which asks for a short label so the specifics are never lost. Every event can carry freeform tags, and the same categories and tags flow through to the shared timeline.
Now you can: record the event the way it really happened, including the off-Amazon and catalog moves that never had a category before.
What can we solve for you?
Reply to this email. It goes to MixShift, and every reply gets a personal answer. If we already solve your problem, we point you at the skill. If we build it, we ship it with your name on the release note.
Don't have the plugin yet? Get it here.
Talk next week.
MixShift