Run Monthly Report Max
Monthly Report Max is the plugin skill that builds your monthly report on top of MixShift Intelligence, rather than assembling it from raw warehouse queries. Ask for it in Claude the same way you would ask for a monthly report ("smart monthly report for [brand], [month]").
What it produces today
Every run produces two documents: a client-ready performance brief you can share as is, and a private internal companion with talking points in call order, the numbers to keep off the call, and every commitment from your last call checked against the data (landed, not landed, or not checkable). Each lives on its own persistent per-brand page that stacks every period's edition, newest on top, so the link you share once is the link your client bookmarks; new months just appear there.
Every core figure is served by the monthly-read request, the same one described in What Intelligence answers. That means the numbers arrive already footing-checked (every piece of a bridge sums exactly to the total change) and carry the engine's own caveats and statements rather than a narrative written cold from a spreadsheet. The report covers month-over-month and year-over-year, with the underlying bridge available for the pieces that moved.
For items flagged with a featured-offer loss, the skill also checks the live offer state on Amazon, so the brief can say whether the box was lost to a competitor or suppressed, and what the fix is.
The skill works on any account, including a brand-new or empty one: without enough history for a normal comparison, it produces a baseline or setup-status read instead of forcing a month-over-month story that is not there yet.
Your forecast, when there is one
When the MixShift forecasting service holds a forecast for the brand that is current for the month being reported, the client brief leads its forecast comparison with the number the forecasting app shows, the current model's projection, named as that with a note that the model has already seen the month. What was forecast before the month closed follows, with its measured error, and it is the only figure a beat or miss is stated against. The internal companion adds what the forecast stands on. When no forecast is published for the brand, the skill asks whether you want a forecast run instead of leaving the section out without a word. A forecast setting turns it off, keeps it in the internal companion only, adds units, or points it at a sub-brand. Where an advertising cost of sale is still settling, the report says the figure "should settle at" a level.
How it falls back
If the account you ask about has Intelligence switched off, the skill says so and offers the standard monthly report instead of quietly running a thinner version of itself. The standard report is the one you already know, built from warehouse data directly rather than from Intelligence.
Related
Shifty is the MixShift docs assistant. Pick a question or open the chat for anything else.