{"id":51447,"plugin_id":"plugin_asdk_app_6ac5ec2359dc8191899aeb18f6d6db6e","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-10-24T13:46:27.256Z","digest":"6ad6ca8c11ef96fecbaec2363401b01fad6f077dba24520bbe667596bc55adfd","against":null,"payload":{"description":"Render RefreshAgent traffic losses, CTR opportunities, content decay, and high-level movement as a focused interactive ChatGPT MCP App. Use when the user wants to inspect or work through SEO changes visually.","included_files":[],"name":"seo-command-center","skill_md_contents":"---\nname: seo-command-center\ndescription: Render RefreshAgent traffic losses, CTR opportunities, content decay, and high-level movement as a focused interactive ChatGPT MCP App. Use when the user wants to inspect or work through SEO changes visually.\n---\n\n# SEO Changes Inbox\n\nTreat this MCP App as a focused changes/opportunities inbox, not a general SEO dashboard.\n\n## Normal flow\n\n1. Resolve the site with `list_connected_sites` when needed.\n2. Call only the deterministic workflow relevant to the user's question:\n   - traffic growth / what is working: `find_biggest_gainers`\n   - traffic decline / what changed: `find_biggest_losers`\n   - CTR upside: `find_ctr_opportunities`\n   - refresh prioritization: `find_content_decay`\n   - high-level context: `compare_search_performance`\n3. Reason over the structured evidence in the host model.\n4. Call `open_seo_command_center` once, passing only the relevant result and a useful `focus`.\n\nDefault `focus` to `losses` when the user asks generally what needs attention. Do not open multiple views pre-emptively; the app loads other workflows lazily when the user selects them.\n\n`assess_information_gain` remains available conversationally, but it is intentionally not a primary inbox view until usage evidence justifies adding it.\n\nDo not attach UI templates to the data tools themselves. The render tool owns the UI resource.\n\nThe app can also be opened directly from ChatGPT's global sidebar or thread panel. It should select the first connected Search Console property and load only the active view.\n\nEach finding's \"Investigate in ChatGPT\" action should hand the evidence back to the host model. RefreshAgent remains BYO-AI: the MCP App and its tools do not invoke a hidden RefreshAgent LLM.\n\n\n## Proactive follow-up\n\nAfter the user investigates a strong Changes Inbox finding, offer at most one supported monitor when it naturally matches the finding:\n\n- losses -> `seo.search_performance_drop`;\n- decay -> `seo.content_decay_detected`;\n- CTR opportunity -> `seo.ctr_opportunity_detected`.\n\nDo not turn opening the UI into an automatic subscription. The user must explicitly choose monitoring, and the current host surface must support MCP Events. Keep the offer outcome-oriented rather than explaining protocol internals unless the user asks.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}