Update to Pilot

{
  "description": "Analyzes Google Search Console data through the Pilot MCP server: queries and pages that gain or lose clicks, pages competing for the same query (cannibalization), click-through rate against position, indexing status of key URLs and sitemaps. Use when the user asks about organic search, SEO performance, Search Console queries or pages. Triggers: Search Console analysis, SEO performance, cannibalization, organic clicks. Déclencheurs : analyse Search Console, requêtes SEO, pages qui perdent des clics, cannibalisation, référencement naturel.",
  "included_files": [],
  "name": "search-console-analysis",
  "skill_md_contents": "---\nname: search-console-analysis\ndescription: \"Analyzes Google Search Console data through the Pilot MCP server: queries and pages that gain or lose clicks, pages competing for the same query (cannibalization), click-through rate against position, indexing status of key URLs and sitemaps. Use when the user asks about organic search, SEO performance, Search Console queries or pages. Triggers: Search Console analysis, SEO performance, cannibalization, organic clicks. Déclencheurs : analyse Search Console, requêtes SEO, pages qui perdent des clics, cannibalisation, référencement naturel.\"\ncompatibility: \"Requires the Pilot MCP server (https://app.pilot.braike.com/mcp) connected in the client and authorized on a workspace with a Search Console site attached.\"\nmetadata:\n  pilot-mcp-server: \"https://app.pilot.braike.com/mcp\"\n  pilot-mcp-tools: \"google_search_console_list_sites google_search_console_get_search_analytics google_search_console_get_url_inspection google_search_console_get_sitemaps\"\n  pilot-mcp-read-only: \"true\"\n---\n\n# Search Console analysis\n\nRead a site's organic search performance and turn it into a short list of pages and queries to work on. Answer in the user's language.\n\n## Requirements\n\n- **Required MCP server:** Pilot MCP (`https://app.pilot.braike.com/mcp`), authorized on the workspace where the site is attached.\n- **Optional MCP servers:** a file storage server to save the tables, a note-taking server to keep the action list. None is needed.\n- **Read-only:** never submit a sitemap or request indexing. Actions are for a person to take.\n\n## Tools\n\n- `google_search_console_list_sites`: the sites attached to the workspace.\n- `google_search_console_get_search_analytics`: clicks, impressions, click-through rate and position, by query, page, country, device or date.\n- `google_search_console_get_url_inspection`: indexing and coverage status of one URL.\n- `google_search_console_get_sitemaps`: submitted sitemaps and their state.\n\n## Steps\n\n1. Call `google_search_console_list_sites`. If several sites are attached, ask which one; pass it as `site_url`. With one site, `site_url` can be left out.\n2. Set two periods of equal length, by default the last 28 days and the 28 days before. Search Console data lags by about two days: end the recent period two days ago.\n3. Call `google_search_console_get_search_analytics` with `dimensions: [\"query\"]` for both periods; then with `dimensions: [\"page\"]`.\n4. Call it again with `dimensions: [\"query\", \"page\"]` on the recent period to find cannibalization: one query whose clicks split across several pages of the site.\n5. Find the pages with many impressions and a click-through rate well below what their position suggests: their title and description deserve work.\n6. For the top pages that lost clicks, call `google_search_console_get_url_inspection` with `inspection_url`. Call `google_search_console_get_sitemaps` once.\n\n## Output\n\n1. **Summary**: clicks and impressions for both periods, and the change.\n2. **Winners and losers**: queries and pages with the largest changes in clicks.\n3. **Cannibalization**: queries split across pages, with the page to keep.\n4. **Low click-through rate**: pages to rewrite, with position and impressions.\n5. **Indexing**: anything wrong found in inspected URLs or sitemaps.\n6. **Action list**: ordered for a person to apply.\n\n## Rules\n\n- Use `row_limit` and narrow the dimensions on large sites: responses over 100,000 characters are cut.\n- Position is an average: compare it only between periods of the same length.\n- Name the period and the search type (`web` by default).\n\n## Examples\n\n- \"Which queries lost clicks over the last 28 days?\"\n- \"Analyse la Search Console du site : pages en baisse et cannibalisation.\"\n- \"Quelles pages ont beaucoup d'impressions mais peu de clics ?\"\n"
}