Source profileQuality 85/100

respira-press/agent-skills-wordpress/skills/respira-site-audit/SKILL.md

respira-site-audit

Use when asked to audit, score, or health-check a WordPress site or page. Runs SEO, AEO, readability, accessibility, performance, RankMath, and Core Web Vitals analyzers and presents a unified report with prioritised fixes.

Source repository stars
40
Declared platforms
0
Static risk flags
0
Last source update
2026-08-04
Source checked
2026-08-05
DecisionCompatibilityInstallWorkflowPermissionsEvidenceSource

Decision brief

What it does—and where it fits

Runs SEO, AEO, readability, accessibility, performance, RankMath, and Core Web Vitals analyzers and presents a unified report with prioritised fixes.

Best for

  • Use when asked to audit, score, or health-check a WordPress site or page.

Not for

  • Tasks that require unconfirmed production actions or broad system permissions.
  • Environments where the pinned source and install steps cannot be inspected.

Compatibility matrix

Platform support, with evidence labels

PlatformStatusEvidenceWhat to check
CodexNot declaredNo explicit evidencePortability before use
Claude CodeNot declaredNo explicit evidencePortability before use
CursorNot declaredNo explicit evidencePortability before use
Gemini CLINot declaredNo explicit evidencePortability before use
Open the compatibility checker

Installation

Inspect first. Install second.

The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

Source-detected install commandSource
npx skills add https://github.com/respira-press/agent-skills-wordpress --skill "skills/respira-site-audit"
Safe inspection promptEditorial

Inspect the Agent Skill "respira-site-audit" from https://github.com/respira-press/agent-skills-wordpress/blob/10821eaabe362fe9052f6ee81ecdd62e5d2f2980/skills/respira-site-audit/SKILL.md at commit 10821eaabe362fe9052f6ee81ecdd62e5d2f2980. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

Workflow

What the source asks the agent to do

  1. 01

    Workflow

    1. respiragetsitecontext. Confirm site URL, active SEO plugin (RankMath, Yoast, AIOSEO, SEOPress), active builder, WooCommerce presence. 2. respiragetbuilderinfo. Note builder type for element-level fix recommendations. 3. respiragetpageoutline if the structure needs to be discu…

    respiragetsitecontext. Confirm site URL, active SEO plugin (RankMath, Yoast, AIOSEO, SEOPress), active builder, WooCommerce presence.respiragetbuilderinfo. Note builder type for element-level fix recommendations.respiragetpageoutline if the structure needs to be discussed.
  2. 02

    Verification

    1. Re-run the analyzer that flagged the issue. 2. Confirm the finding no longer appears at the same severity level. 3. For SEO fixes, note that index refresh and ranking changes are delayed. Tell the user.

    Re-run the analyzer that flagged the issue.Confirm the finding no longer appears at the same severity level.For SEO fixes, note that index refresh and ranking changes are delayed. Tell the user.
  3. 03

    Common Mistakes

    Review the “Common Mistakes” section in the pinned source before continuing.

    Review and apply the “Common Mistakes” source section.
  4. 04

    Inputs

    Target: a specific page URL, page ID, or "the whole site".

    Target: a specific page URL, page ID, or "the whole site".Scope: which analyzers to run. Default is all eight.Output format: a summary for the user, or JSON for a CI / CD pipeline.
  5. 05

    Single-page audit

    1. respiragetsitecontext. Confirm site URL, active SEO plugin (RankMath, Yoast, AIOSEO, SEOPress), active builder, WooCommerce presence. 2. respiragetbuilderinfo. Note builder type for element-level fix recommendations. 3. respiragetpageoutline if the structure needs to be discu…

    respiragetsitecontext. Confirm site URL, active SEO plugin (RankMath, Yoast, AIOSEO, SEOPress), active builder, WooCommerce presence.respiragetbuilderinfo. Note builder type for element-level fix recommendations.respiragetpageoutline if the structure needs to be discussed.

Permission review

Static risk signals and limitations

No configured static risk pattern was detected

This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.

Evidence record

Why each signal appears

EvidenceSourceComputedTestedEditorial
SignalValueEvidence typeMeaning
Quality score85/100ComputedDocumentation, specificity, maintenance, and trust rules
Repository stars40SourceRepository attention, not individual Skill quality
Compatibility0 platformsSourceDeclared in the catalog source record
Usage guideautomated source guideEditorialGenerated or reviewed according to the visible evidence level

Pinned source

Provenance and original SKILL.md

Repository
respira-press/agent-skills-wordpress
Skill path
skills/respira-site-audit/SKILL.md
Commit
10821eaabe362fe9052f6ee81ecdd62e5d2f2980
License
MIT
Collected
2026-08-05
Default branch
main
View the original SKILL.md

Respira Site Audit

Common Mistakes

MistakeCorrect approach
Running analyzers without knowing which page to auditAlways confirm the target. Site-wide (all public pages) or a specific page URL or ID.
Reporting raw analyzer output without prioritisingGroup findings by severity (CRITICAL, WARNING, SUGGESTION) and surface quick wins first.
Running all analyzers in sequence when only one is neededMatch 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 issuesBuilder 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 interchangeableSEO 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 auditingDrafts and private pages may produce incomplete results. Confirm status: publish first.
Using extract_builder_content when you only need structureUse respira_get_page_outline for the "what is on this page" read. It is lighter and includes the primary heading per row.

Inputs

  • Target: a specific page URL, page ID, or "the whole site".
  • Scope: which analyzers to run. Default is all eight.
  • Output format: a summary for the user, or JSON for a CI / CD pipeline.

Workflow

Single-page audit

  1. respira_get_site_context. Confirm site URL, active SEO plugin (RankMath, Yoast, AIOSEO, SEOPress), active builder, WooCommerce presence.
  2. respira_get_builder_info. Note builder type for element-level fix recommendations.
  3. respira_get_page_outline if the structure needs to be discussed.
  4. Run analyzers in parallel where possible:
    • respira_analyze_seo. Title, meta description, headings, internal links, canonical.
    • respira_analyze_aeo. Structured content, FAQ schema, answer-box signals.
    • respira_analyze_readability. Flesch score, sentence length, passive voice.
    • respira_analyze_performance. Load time, image sizes, render-blocking resources.
    • respira_scan_page_accessibility. WCAG 2.1 AA violations, alt text, contrast.
    • respira_analyze_images. Per-image weight, format, oversize-by-X factor.
    • respira_check_structured_data. Schema.org presence per page.
    • respira_get_core_web_vitals. CrUX-backed LCP, INP, CLS where available.
  5. Aggregate findings by severity: CRITICAL → WARNING → SUGGESTION.
  6. Build a prioritised fix list: quick wins first (alt text, missing meta) before structural changes.
  7. Report: headline score per area plus top 3 fixes per area.

Site-wide audit

  1. respira_list_pages with status: publish. Collect all published page IDs.
  2. For each page, or a representative sample, run the single-page workflow above.
  3. Aggregate into a site-level summary: worst-performing pages, most common issue types, overall score bands.

RankMath / Yoast integration

If RankMath, Yoast, AIOSEO, or SEOPress is active (visible in respira_get_site_context):

  • respira_analyze_rankmath reads RankMath's own focus keyword scores and suggestions.
  • Use these scores alongside respira_analyze_seo for a richer picture. Don't run them as alternatives.
  • respira_check_seo_issues returns the active SEO plugin's own issue feed.

Rules

  • Always run respira_get_site_context first. Plugin presence (RankMath, Yoast, WooCommerce, ACF, WPML) changes which tools are relevant.
  • Severity taxonomy: every finding must be CRITICAL (broken or missing, hurts rankings or UX), WARNING (suboptimal, addressable), or SUGGESTION (optional improvement).
  • Do not recommend changes that bypass the builder. For element-level SEO fixes (alt text, heading hierarchy), use respira_find_element plus respira_update_element after confirming the builder.
  • For accessibility fixes, prefer respira_apply_accessibility_fixes over manual element edits where the tool covers the finding.
  • Performance findings are informational. Do not modify theme files or plugins to address them. Surface the issue and recommend the appropriate plugin or hosting action.
  • For WPML-active sites, the audit is per-language. Pass the lang parameter to scope the run.

Verification

After applying a fix:

  1. Re-run the analyzer that flagged the issue.
  2. Confirm the finding no longer appears at the same severity level.
  3. For SEO fixes, note that index refresh and ranking changes are delayed. Tell the user.

For site-wide audits, re-audit the 3 worst-performing pages after fixes to confirm score movement.

Escalation

Stop and ask the user if:

  • The site has more than 200 published pages and the request is "audit the whole site". Confirm how many pages to sample.
  • A CRITICAL finding requires a structural change (no H1 on any page, no <html lang> attribute). These often need theme or plugin changes beyond Respira's scope.
  • respira_analyze_performance returns LCP > 4s or CLS > 0.25. Flag as high priority and ask whether to involve a developer.
  • The site is on a multi-site network and the audit target wasn't specified. Confirm whether the run is per-subsite or network-wide.

Example

Goal: audit the homepage for SEO and AEO readiness.

1. respira_get_site_context        → WordPress 6.9, RankMath active, Elementor 3.21
2. respira_get_builder_info        → Elementor, supported
3. respira_analyze_seo             → CRITICAL: no meta description | WARNING: 3 images missing alt
4. respira_analyze_aeo             → WARNING: no FAQ schema | SUGGESTION: add HowTo schema
5. respira_analyze_rankmath        → Focus keyword score: 62/100, improve keyword density
6. respira_scan_page_accessibility → WARNING: 2 buttons have no accessible label
7. respira_get_core_web_vitals     → LCP 2.8s (needs improvement), INP 180ms (good), CLS 0.05 (good)

Report:
  CRITICAL  → Add meta description (missing entirely)
  CRITICAL  → Add alt text to 3 hero images
  WARNING   → Add FAQ schema block for AEO (AI answer-box eligibility)
  WARNING   → 2 buttons need aria-label for screen readers
  WARNING   → LCP at 2.8s, target sub-2.5s by deferring the hero video
  SUGGESTION → Increase focus keyword density from 0.4% to 0.8%

Alternatives

Compare before choosing

Computed 9313,363

AgriciDaniel/claude-seo

seo-ecommerce

E-commerce SEO analysis: Google Shopping visibility, Amazon marketplace intelligence, product schema validation, competitor pricing analysis, and marketplace keyword gaps. Combines on-page product SEO with marketplace data from DataForSEO Merchant API. Use when user says "ecommerce SEO", "product SEO", "Google Shopping", "marketplace SEO", "product schema", "Amazon SEO", "product listings", "shopping ads", or "merchant SEO".

2026-07-270 platforms
Computed 9340

respira-press/agent-skills-wordpress

seo-aeo-amplifier

Use when the user says 'run an seo aeo audit', 'improve my search visibility', 'optimize my site for search engines', or wants the site cited by AI answer engines. Audits on-page SEO and AEO, generates schema markup, and applies fixes on duplicates for review after a snapshot.

2026-08-040 platforms
Computed 923,318

nowork-studio/NotFair

seo-analysis

Full SEO audit: Google Search Console data + URL Inspection API + PageSpeed Insights API + technical crawl + keyword research + metadata audit + schema markup audit + search intent analysis + Core Web Vitals monitoring. Feeds real GSC data and PageSpeed metrics into AI to surface quick wins, diagnose traffic drops, find content gaps, identify metadata mismatches, detect schema gaps, monitor page performance, and produce an actionable 30-day plan. Use this skill whenever the user asks about SEO,

2026-07-310 platforms
Computed 922,509

aaron-he-zhu/aaron-marketing-skills

performance-monitor

Use it for seo audit and marketing tasks; the detail page covers purpose, installation, and practical steps.

2026-08-051 platforms