{"id":49831,"plugin_id":"plugin_asdk_app_6abd56e34b34819182293d4c7884f8a1","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-10-24T13:41:23.122Z","digest":"2659c596b17dc12222288ac9ef80e359a1259afbfd63cf13934bea6dd6e4d216","against":null,"payload":{"description":"Benchmark a site's AI search readiness against named competitors with Glippy, find the categories where it trails, and rank the gaps worth closing first.","included_files":[],"name":"competitor-benchmark","skill_md_contents":"---\nname: competitor-benchmark\ndescription: Benchmark a site's AI search readiness against named competitors with Glippy, find the categories where it trails, and rank the gaps worth closing first.\n---\n\n# Benchmarking against competitors\n\nUse this when the user wants to know how their site compares with competitors for AI search, or asks \"who is doing GEO best in my market\".\n\n## Get the list of sites\n\n- Ask the user for their own domain and the competitors to include. Use only domains the user named. If they ask you to suggest competitors, you may propose some, but confirm the list before running anything.\n- `compare_domains` takes 2 to 8 domains. If the user names more, ask which 8 matter most.\n- Decide each homepage's page type before the call and pass it as `page_type`, as a map when the sites differ (for example a one-page local business is \"service\"). A re-run with another page type is a new analysis.\n\n## Run one comparison\n\nCall `compare_domains` once with all the sites. Do not also run `analyze_domain` on each site unless the user asks for one site's full report. If a site could not be analysed (robots.txt, unreachable, rate limit), say so and benchmark the rest. Do not retry.\n\n## Read the result\n\nLead with the ranking: the user's site position, its score, and the leader's score. Then:\n\n1. **Gaps.** Categories where the user's site trails the best competitor by about 15 points or more. These are where competitors are visibly ahead.\n2. **Strengths.** Categories where the user's site leads. Tell them to keep these.\n3. **Shared weaknesses.** Categories where every site scores low. Fixing these is a chance to lead the whole market, not just catch up.\n\n## Rank what to do first\n\nOrder the gaps by what AI answer engines depend on most: Machine Readability first (it includes whether robots.txt lets AI crawlers in at all), then Structured Data & Schema, Entity & Authority and Citability & Answer-Readiness, then the rest. Within that, prefer fixes that are cheap to ship, such as adding JSON-LD or meta tags, over large content projects. Give three to five steps, each tied to a category and a competitor that does it better.\n\nOffer to draft the fixes (see the draft-fixes skill) or to run the full report on the user's own site.\n\n## Limits to state\n\n- Each site is judged on its homepage only, so this compares homepages, not whole sites.\n- Scores measure readiness signals on the page. They do not measure how often AI engines actually cite each site.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}