← MWM AICONTENT HISTORY
WHAT CHANGED
Update to MWM AI
Snapshot Nov 16, 2026 · 18:15 UTC · version 0.32.2
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save MWM AI and check future changes in Following.
Up to 3 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "The person's own app numbers: revenue and proceeds, subscriptions, users, retention, installation cohorts, lifetime value, publishing figures and product analytics, read and compared correctly. Use when the person says things like \"how is my revenue doing?\", \"did the new paywall work?\", \"why did my users drop?\", \"what is my LTV?\" or \"compare this month with last month\". Not for competitors' numbers (market-research) or ratings and reviews (reviews).",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 375
}
],
"name": "app-analytics",
"skill_md_contents": "---\nname: app-analytics\ndescription: \"The person's own app numbers: revenue and proceeds, subscriptions, users, retention, installation cohorts, lifetime value, publishing figures and product analytics, read and compared correctly. Use when the person says things like \\\"how is my revenue doing?\\\", \\\"did the new paywall work?\\\", \\\"why did my users drop?\\\", \\\"what is my LTV?\\\" or \\\"compare this month with last month\\\". Not for competitors' numbers (market-research) or ratings and reviews (reviews).\"\n---\n\n# App analytics\n\n## When this applies\n\nReading the person's own numbers: store revenue and proceeds, subscriptions, users and retention, installation cohorts, lifetime value, publishing revenue and spend, and product analytics from MWM's SDK. Competitors' figures belong to market-research; ratings and reviews to reviews.\n\n## The job and what good looks like\n\nEvery number is named: which metric, a period flow or an installation cohort, gross or net, which currency, which window and how mature the data is. Comparisons put like with like. Figures come from the reads, with their date and their limits; an absent value is unknown, never zero. A change is explained only as far as the data supports it, and a guess is labelled as one.\n\n## How a pro decides\n\n- **Which revenue.** When the answer differs between gross revenue and proceeds, or between store and publishing figures, ask which one; otherwise use proceeds and say so.\n- **Cohort or period.** A cohort follows the users who installed on a date; a period counts what happened on calendar days. They answer different questions and never share a comparison.\n- **Is it mature.** A cohort or a bucket still filling up is not a drop. Compare windows of equal length and equal maturity.\n- **One dimension at a time.** Split by one dimension, read it, and narrow before splitting again.\n- **Before and after.** For a paywall or a release, compare equal windows around the change, and say what else changed in the same days when the data shows it.\n\n## Do\n\n- Name each number fully the first time you give it.\n- Keep each currency in its own column.\n- Explain only what the data shows, and mark the rest as a hypothesis.\n- Ask when two readings of the question would give different answers.\n- Write a note on a chart when the person asks for one, with facts from the data read.\n\n## Don't\n\n- Don't mix cohort and period figures, two currencies, or store and publishing revenue in one table.\n- Don't read an immature cohort as a fall.\n- Don't treat a missing value as zero.\n- Don't call search visibility traffic, visits or conversion.\n- Don't add a chart note nobody asked for.\n\n## Pitfalls\n\n- Monthly recurring revenue normalises plans to a month; it is not what was booked.\n- User retention, subscription renewal and SDK event retention are different measures with similar names.\n- Reports can lag, so the latest days may be incomplete.\n- Lifetime value forecasts are predictions, in their own currency, with fewer filters than store figures.\n\n## Store facts\n\nTool results carry the store rules and limits they depend on, each with its source and the date it was checked. `get_publishing_knowledge` answers questions on this skill's topics the same way (topics: `mwm/analytics-metric-definitions`). When you use one of these facts, give its source and date.\n"
}SHA-256 of public snapshot: 7c9e2146b87eaf96d92b7e7cbfe676a3af651e0b1e52a244e92c34d076d1f5b7