{"id":52236,"plugin_id":"plugin_asdk_app_6ac9bca799288191879d0c198d8c8a92","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-10-24T13:49:05.824Z","digest":"484ac50c3c3243e56ce49356d2ca42935479d57bd847e4d70feaf28c021b4b70","against":null,"payload":{"description":"List and categorize the WordPress plugins a website uses, including its page builder, SEO, caching, forms, e-commerce, membership or multilingual plugins. Use before calling ThemeSniffer's get_wordpress_tech_stack tool whenever the user asks which plugins or page builder a site uses, or wants to add the same features to their own site.","included_files":[{"relative_path":"agents/openai.yaml","size_in_bytes":244},{"relative_path":"references/plugin-categories.md","size_in_bytes":3745}],"name":"detect-wordpress-plugins","skill_md_contents":"---\nname: detect-wordpress-plugins\ndescription: List and categorize the WordPress plugins a website uses, including its page builder, SEO, caching, forms, e-commerce, membership or multilingual plugins. Use before calling ThemeSniffer's get_wordpress_tech_stack tool whenever the user asks which plugins or page builder a site uses, or wants to add the same features to their own site.\n---\n\n# Detect a website's WordPress plugins\n\nUse the ThemeSniffer connector to find the plugins a site uses, group them so\nthey're easy to scan, and be clear about what can't be detected.\n\n## Steps\n\n1. **Get the URL** the same way as for theme detection: accept bare domains,\n   add `https://`, drop tracking parameters, one site per check.\n2. **Run the detection** with the ThemeSniffer connector's\n   `get_wordpress_tech_stack` tool, passing the URL as `url`. It also returns\n   the theme; include it in one line at the top of the answer. If\n   `isWordPress` is `null`, `blocked` is true or the result is an error, the\n   page couldn't be read: report that (with `note`) instead of a plugin list,\n   and don't call it \"not WordPress\". If `isWordPress` is `false`, say the\n   site doesn't appear to run WordPress, so there are no WordPress plugins to\n   list.\n3. **Group the plugins.** Each plugin has `name`, `slug`, `known`, and\n   usually `category`, `premium` and `version`. Use `category` when it's\n   specific. When it's missing or `\"Other\"`, read\n   `references/plugin-categories.md` before writing the answer and match by\n   slug or name; for example `ultimate-addons-for-gutenberg` is Spectra, a\n   page builder. If a plugin isn't listed there but its name plainly states\n   what it does (for example \"Instagram Feed\" or \"Cookie Consent\"), group it\n   by that. Put only the plugins that are still unclear under \"Other\".\n   - `known: false` means ThemeSniffer title-cased the name from the folder\n     slug. Use the reference's real name when it has one; otherwise keep the\n     name as given.\n4. **Answer** in this shape:\n\n   ```\n   **<site>** runs WordPress with the <Theme> theme and <N> detected plugins.\n\n   **Page builder**\n   - <Plugin name> <(premium) when `premium` is true>\n\n   **SEO**\n   - ...\n\n   Note: only plugins that leave traces on the public pages can be detected.\n   Backend-only plugins (backups, security scanners, admin tools) won't show up.\n   ```\n\n   - Order categories by how useful they are for rebuilding the site: page\n     builder, e-commerce, SEO, forms, caching/performance, then the rest.\n   - Show a version only if the result reports one, and don't present it as\n     certain. Mark a plugin premium only when `premium` is true.\n   - The result has no plugin links. Don't add any unless the user asks; then\n     link only a wordpress.org page you know exists, or say where to look.\n   - If the user asked about one kind of plugin (\"which SEO plugin?\"), answer\n     that first in one line, then offer the full list.\n5. **Add the caveat** about undetectable plugins every time. If no plugins\n   were found, say that this doesn't mean the site has none.\n\n## Rules\n\n- Never invent plugins, versions, prices or links. Report only what the\n  connector returned or what you saw on the page yourself.\n- Don't paste raw tool output.\n- Don't make security claims (for example \"this version is vulnerable\")\n  unless the connector's result says so.\n- Only analyze sites the user asked about.\n\n## If the connector isn't available\n\nTell the user that connecting the ThemeSniffer connector (the MCP server\nbundled with this plugin) gives the most complete result. If you can fetch web\npages, look for `/wp-content/plugins/<slug>/` in the page's asset URLs, plugin\nHTML comments and generator meta tags, map slugs with\n`references/plugin-categories.md`, and label the answer as a manual check.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}