{"id":98779,"plugin_id":"plugin_asdk_app_6accf624ea808191980d359c299fae66","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-16T18:15:27.278Z","digest":"49e653ad7aa271461e34a63a3a906797427bcd0c269797b6b0582c2569709038","against":null,"payload":{"description":"Timed moments on the stores: App Store in-app events and Google Play promotional content, from the idea and the theme to the artwork, the texts, the dates and the submission. Use when the person says things like \"plan an event for Halloween\", \"announce our big update on the store\", \"a challenge for my users\", \"promote our sale on Google Play\" or \"when should I submit my event?\". Not for pages per audience (acquisition-pages) or the listing's screenshots (store-visuals).","included_files":[{"relative_path":"agents/openai.yaml","size_in_bytes":359}],"name":"live-moments","skill_md_contents":"---\nname: live-moments\ndescription: \"Timed moments on the stores: App Store in-app events and Google Play promotional content, from the idea and the theme to the artwork, the texts, the dates and the submission. Use when the person says things like \\\"plan an event for Halloween\\\", \\\"announce our big update on the store\\\", \\\"a challenge for my users\\\", \\\"promote our sale on Google Play\\\" or \\\"when should I submit my event?\\\". Not for pages per audience (acquisition-pages) or the listing's screenshots (store-visuals).\"\n---\n\n# Live moments\n\n## When this applies\n\nPlanning, designing and scheduling a moment the stores show for a limited time: an in-app event on the App Store or promotional content on Google Play, for a season, a challenge, new content, an offer or a major update. Pages per audience belong to acquisition-pages; the listing's own screenshots to store-visuals.\n\n## The job and what good looks like\n\nA moment with a clear theme: what happens, for whom, and what they get. \"Winter challenge: one new beat each evening for a week, with a frost sample pack as the reward\" beats \"winter event\". The artwork is on brand with the app's past moments, the texts fit each language, and the dates leave the stores time to review. On both stores, one theme and one look.\n\n## How a pro decides\n\n- **Which kind of moment.** The kind follows what happens: a goal to reach, a ranking, something live, new content, a premiere, a major update. Its defaults fit most moments; change them only for a reason.\n- **Which moment matters most.** Give the highest priority to the one moment that matters this period, not to every one.\n- **Brand continuity.** The artwork follows the app's brand guide and references as brand-visuals describes; start from a past event's card when there is one, and say which one guided the colours and composition.\n- **When to submit.** Plan back from the start date, leaving room for a review and for a second one after a rejection; check the review times in the knowledge base before promising a date.\n- **Featuring.** Ask before requesting a store feature: it spends something the person may want later.\n\n## Do\n\n- Write an offer's tagline so it says what is discounted and by how much.\n- Say the dates in the person's time zone and in UTC.\n- Use the same theme and look on both stores when the moment runs on both.\n- Keep the person's studio edits with every iteration.\n- Build each iteration on the last draft.\n\n## Don't\n\n- Don't localize before the person confirmed the primary language's texts and artwork.\n- Don't make artwork per language unless one needs it, such as text on the card or a local visual.\n- Don't schedule a moment without checking the review time in the knowledge base.\n- Don't start from scratch at each iteration.\n- Don't create again an event the studio already created; read its result.\n\n## Pitfalls\n\n- An event approved after its start date never shows.\n- Google Play lays its own text and icon over the image, so an image with words or a logo clashes.\n- An event created halfway exists: fix or delete it instead of creating another.\n- Reading the rules and the app's events again when a brief from MWM Console already carries them wastes the person's time.\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: `app-store/in-app-events`, `google-play/promotional-content`, `aso/event-practice`). When you use one of these facts, give its source and date.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}