{"id":68033,"plugin_id":"plugin_asdk_app_6acd50614df481919627628425b1b357","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-10-28T13:12:14.071Z","digest":"e6ad8467eb5e31f8072edb24c53d7ad2b1cd73eae09a2db0451915af78dc482f","against":null,"payload":{"description":"Query Kipify marketing metrics across Meta Ads, Google Ads, GA4, Search Console, Shopify, Magento, and blended Kipify metrics via the connected Kipify MCP server.","included_files":[],"name":"analyze-marketing-metrics","skill_md_contents":"---\nname: analyze-marketing-metrics\ndescription: Query Kipify marketing metrics across Meta Ads, Google Ads, GA4, Search Console, Shopify, Magento, and blended Kipify metrics via the connected Kipify MCP server.\n---\n\n# Analyze marketing metrics with Kipify\n\nUse this skill when the user asks about ads performance, ecommerce metrics, SEO search demand, or cross-channel marketing results available through their Kipify account.\n\n## Prerequisites\n\n- The Kipify MCP server must be connected and authorized.\n- Prefer tools that match the granted OAuth scopes. If a tool returns authentication or insufficient-scope errors, ask the user to reconnect Kipify and grant the needed connectors.\n\n## Workflow\n\n1. Call `list_my_connectors` to see which connectors the user authorized.\n2. Call `list_accounts` for the relevant connector before querying, then use only returned account IDs / property IDs / site URLs.\n3. Call `list_metrics_catalog` to resolve metric keys, splits, and filters for that connector type.\n4. Call `query_metrics` with explicit date range, metrics, and optional splits/filters.\n5. If `has_more` is true, paginate with `offset` / `next_offset` until complete or the user asks for a summary of the first page.\n6. For Google Search Console SEO deep-dives, use `analyze_search_console` with `opportunities`, `cannibalization`, or `search_appearance` when that fits better than a raw metric query.\n7. For database connectors with SQL access, use `list_schema` / `profile_table` before `run_readonly_sql`. Prefer catalog/query_metrics when virtual metrics exist.\n\n## Output rules\n\n- Cite the connector, account, date range, and metric keys used.\n- Do not invent metrics or account IDs that were not returned by tools.\n- Surface sampling, thresholding, or compatibility warnings from the tool response when present.\n- Refuse destructive, write, payment, or out-of-scope account access requests.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}