respira-site-audit
Installation
SKILL.md
Respira Site Audit
Common Mistakes
| Mistake | Correct approach |
|---|---|
| Running analyzers without knowing which page to audit | Always confirm the target. Site-wide (all public pages) or a specific page URL or ID. |
| Reporting raw analyzer output without prioritising | Group findings by severity (CRITICAL, WARNING, SUGGESTION) and surface quick wins first. |
| Running all analyzers in sequence when only one is needed | Match the analyzer to the question. If the user asks about SEO only, run respira_analyze_seo and skip the rest. |
Skipping respira_get_builder_info before reporting element-level issues |
Builder type affects which fixes are possible. Elementor, Divi 4, Divi 5, Bricks, Beaver, and Oxygen all have different fix paths. |
| Treating AEO and SEO as interchangeable | SEO targets search rankings. AEO targets AI-generated answers. Both analyzers cover different signals and you usually want both. |
| Not checking whether the page is published before auditing | Drafts and private pages may produce incomplete results. Confirm status: publish first. |
Using extract_builder_content when you only need structure |
Use respira_get_page_outline for the "what is on this page" read. It is lighter and includes the primary heading per row. |
| Calling a site secure because a security plugin is installed | Run respira_run_security_audit and report what it checked and what it could not. A partial scan or an unavailable vulnerability check is never "clean". |
Quoting respira_get_core_web_vitals as real-user data |
It is a heuristic estimate from static analysis. Use respira_run_pagespeed_audit for Lighthouse lab data and CrUX field data. |