{"id":44972,"plugin_id":"plugin_asdk_app_6a9a0d539a68819185fe2d4e9032c0f3","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-10-24T13:20:01.216Z","digest":"5d7799e3799cf8a1284f58bb19947d9f4d8884c17d560679b696ed7bc7c96ba7","against":null,"payload":{"description":"Check that a newly connected MerchantFlow store is ready - integrations healthy, cost data covered, plan limits understood - then show the merchant what to ask first. Runs when the user chooses Set up for MerchantFlow or asks how to get started.","included_files":[],"name":"get-started","skill_md_contents":"---\nname: get-started\ndescription: Check that a newly connected MerchantFlow store is ready - integrations healthy, cost data covered, plan limits understood - then show the merchant what to ask first. Runs when the user chooses Set up for MerchantFlow or asks how to get started.\n---\n\n# Get started with MerchantFlow\n\nThe merchant has just connected MerchantFlow. Your job is a short readiness\ncheck, then one good first answer. Keep it brief: a few lines per step, real\nfigures only, no invented numbers. The user's own instructions always take\nprecedence over this skill - if they ask for something specific, do that\ninstead and skip the rest.\n\n## 1. Check the connection\n\nCall `get_integration_status` with `{}`.\n\n- Say which store platform and ad platforms are connected and when each last\n  synced.\n- If a sync is failing or an integration reports an error, say so plainly and\n  point them to Settings > Integrations in the MerchantFlow dashboard. Do not\n  guess at the cause.\n- If the store's first import is still running (`_meta.sync_status` is\n  `initial_sync_running` on any response), tell them figures are incomplete\n  until it finishes and that they can come back later. Stop here.\n\n## 2. Check cost data\n\nCall `get_cogs_coverage` with `{}` (it defaults to the last 30 days).\n\n- Report the share of revenue covered by product costs (COGS).\n- If coverage is below about 90%, explain in one sentence that profit is\n  overstated for products without a cost, and offer to list the gaps with\n  `find_cogs_gaps`. Costs are added in the dashboard under COGS.\n- If coverage is complete, say so in one line and move on.\n\n## 3. Explain what this connection covers\n\nCall `list_capabilities` with `{}` and state, in one or two lines, how far back\ntheir plan's history goes and whether combined figures across several stores\nare available. Do not describe plans they are not on, and do not suggest\nupgrading.\n\n## 4. First answer\n\nCall `get_pnl_summary` for the last 30 days in their store's timezone and give\nthe headline: net revenue, net profit, net margin, and the single largest cost\nline. One short paragraph.\n\n## 5. Show them where to go next\n\nOffer three follow-ups they can ask, chosen from what you just saw, for example:\n\n- \"Which products lost money last month?\"\n- \"Compare Meta and Google ad performance over the last 90 days.\"\n- \"What changed in my profit this week versus last week?\"\n\nThen mention, once:\n\n- **Profit waterfall** in the ChatGPT sidebar opens the interactive chart on\n  any recent period.\n- They can ask ChatGPT to act when something happens in their store - when a\n  sync finishes, when MerchantFlow detects an anomaly, or when their Daily AI\n  Summary arrives (the summary must be turned on under Settings >\n  Notifications in MerchantFlow).\n\nIf they installed MerchantFlow in the middle of another task, return to that\ntask in the same conversation after this check.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}