Update to ThemeSniffer

{
  "description": "Report a website's full WordPress stack - theme, page builder, plugins and hosting - or compare several sites. Use before calling ThemeSniffer's tools whenever the user asks for a site's theme and plugins together, what a site is built with, or how several sites compare (competitor research, client prospecting, migration or redesign scoping).",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 244
    }
  ],
  "name": "wordpress-site-audit",
  "skill_md_contents": "---\nname: wordpress-site-audit\ndescription: Report a website's full WordPress stack - theme, page builder, plugins and hosting - or compare several sites. Use before calling ThemeSniffer's tools whenever the user asks for a site's theme and plugins together, what a site is built with, or how several sites compare (competitor research, client prospecting, migration or redesign scoping).\n---\n\n# WordPress stack report and comparison\n\nCombine theme and plugin detection into one report, and for several sites,\na side-by-side comparison.\n\n## Steps\n\n1. **Collect the URLs.** Normalize each one (add `https://`, drop tracking\n   parameters, remove duplicates). For more than 10 sites, confirm with the\n   user before running, since each site is a separate check.\n2. **Detect each site** with the ThemeSniffer connector's\n   `get_wordpress_tech_stack` tool, one site at a time (it is rate limited).\n   Keep going if one site fails or is blocked and report that in its row.\n3. **Interpret each result** the same way as the `detect-wordpress-theme` and\n   `detect-wordpress-plugins` skills (child themes, custom themes, page\n   builders, not WordPress).\n4. **Write the report.**\n\n### One site\n\n```\n## <site>\n\n**Theme:** <Theme> (<parent, if child theme>) - <free / likely premium / likely custom>\n**Page builder:** <name or \"none detected\">\n**E-commerce:** <name or \"none detected\">\n**SEO:** <name or \"none detected\">\n**Hosting / CDN:** <hosting.name and cdn.name, or \"not identified\">\n\n**All detected plugins** (<N>)\n<grouped list as in detect-wordpress-plugins>\n\n**Notes**\n- <only observations the data supports, see below>\n```\n\n### Several sites\n\nStart with a comparison table, one column per site:\n\n```\n| | site-a.com | site-b.com |\n| - | - | - |\n| WordPress | Yes | Yes |\n| Theme | Astra | Custom (agency-x) |\n| Page builder | Elementor | none detected |\n| E-commerce | WooCommerce | - |\n| SEO | Rank Math | Yoast SEO |\n| Caching | WP Rocket | LiteSpeed Cache |\n| Plugins detected | 14 | 9 |\n| Hosting / CDN | Kinsta / Cloudflare | not identified / - |\n| Speed snapshot | 74 (Fair) | 88 (Good) |\n```\n\nThe speed figure is `performance.score` and `grade`: a single lab\nmeasurement from ThemeSniffer's servers, useful for comparing sites in the same\nrun, not real visitor Core Web Vitals. Say so if you show it. Hosting or CDN\n\"not identified\" means no header signature matched, not that there is none.\n\nThen:\n- **Shared:** plugins every site uses.\n- **Differences** that matter for the user's goal (for example different\n  page builders or store platforms).\n- A per-site plugin list only if the user asks, or if there are 3 sites or\n  fewer.\n\n## What to put in Notes\n\nOnly observations the data supports, such as:\n\n- More than one plugin doing the same job (two SEO or two caching plugins).\n- A page builder plus a theme that has its own builder.\n- Not WordPress, or a custom theme that can't be bought.\n- An outdated theme (`theme.outdated`), or missing security headers from\n  `security`, only as reported.\n\nDon't speculate about performance, security or traffic beyond what the\nresult reports.\n\n## Rules\n\n- Never invent themes, plugins, versions or links.\n- Always end with the caveat that backend-only plugins can't be detected.\n- Only analyze the sites the user named.\n"
}