{"id":99402,"plugin_id":"plugin_asdk_app_6af5a2f86fb08191b3ca6d9f00760a12","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-16T18:17:30.902Z","digest":"fc7e4a88b8ab3323980a1f378d106f3e492cf3ae9db6fe6d9b7693ac2f76c091","against":null,"payload":{"description":"Analyze the user's connected Google Search Console (GSC) properties with LoomaScale. Use for SEO reports, organic traffic drops, search queries, keyword opportunities, low click-through rate (CTR), average position, URL indexing status and sitemap errors. Read-only. Do not invoke for general SEO definitions, live rank tracking, website crawling, requesting indexing, or Google Ads and Google Analytics reports.","included_files":[{"relative_path":"agents/openai.yaml","size_in_bytes":522},{"relative_path":"references/search-console.md","size_in_bytes":2440}],"name":"loomascale-gsc","skill_md_contents":"---\nname: loomascale-gsc\ndescription: Analyze the user's connected Google Search Console (GSC) properties with LoomaScale. Use for SEO reports, organic traffic drops, search queries, keyword opportunities, low click-through rate (CTR), average position, URL indexing status and sitemap errors. Read-only. Do not invoke for general SEO definitions, live rank tracking, website crawling, requesting indexing, or Google Ads and Google Analytics reports.\n---\n\n# Google Search Console with LoomaScale\n\nAnswer SEO and organic search questions with evidence from the user's connected\nGoogle Search Console (GSC) account: traffic changes, keyword and page opportunities,\nlow CTR, indexing status and sitemap errors. This package connects to\n`https://api.loomascale.com/mcp/gsc`. Inspect\navailable tool descriptions and input schemas; a client may add a namespace to\nthe tool names used here.\n\n## Resolve the property\n\nReuse a property already verified in the conversation. Otherwise call\n`gsc_list_sites` and pass `site_url` exactly as listed (`sc-domain:example.com` or a\nURL-prefix property). It can be omitted when exactly one property is reachable. If\nseveral fit and the task does not identify one, ask which to use.\n\n## Choose the tool that answers the question\n\n| Question | Tool |\n| --- | --- |\n| Which properties can I access? | `gsc_list_sites` |\n| Why did organic traffic change? | `gsc_compare_periods` |\n| Which queries or pages should I improve first? | `gsc_find_keyword_opportunities`, `gsc_find_page_opportunities` |\n| Clicks, impressions, CTR or position by query, page, country, device or date | `gsc_query_search_analytics` |\n| Is this URL indexed, and which canonical did Google pick? | `gsc_inspect_url` |\n| Were my sitemaps processed? | `gsc_list_sitemaps` |\n\nRead [Search Console tools](references/search-console.md) for date windows,\nfilters, pagination and coverage limits.\n\n## Stay read-only\n\nEvery tool reads. Nothing requests indexing, submits or deletes a sitemap, or\nchanges a setting; say so when the user asks, and point to Search Console.\n\n## Handle access and helper tools accurately\n\n- If authorization is missing, expired or lacks a permission, use the link the\n  tool returns or the [LoomaScale connections dashboard](https://loomascale.com/dashboard/connections).\n  A refusal that names the user's role is Google judging the login's access, not\n  something reconnecting fixes.\n- For a usage-limit refusal, call `loomascale_check_quota` once and explain the\n  allowance or reset it reports. A usage allowance is not an ad budget.\n- `loomascale_request_feature` sends a message to the LoomaScale team. Call it\n  only when the user asks to send a feature request.\n\n## Return a result the user can assess\n\nName the property and exact dates (Pacific time). Say whether recent partial days are included. Separate observed changes from possible causes, and label click potential as an estimate.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}