/wordpress-site-dna

name: wordpress-site-dna
description: "Use when the user says 'analyze my wordpress site', 'what is running on my site', 'site dna', or 'what plugins are on my site'. Detects every page builder, audits active versus dead-weight plugins, maps content structure, finds orphaned shortcodes, and checks performance and security posture."
license: MIT
metadata:
  author: Respira for WordPress
  author_url: https://respira.press
  version: 1.3.0
  mcp-server: respira-wordpress
  category: audit
  respira_min_version: 8.9.0

WordPress Site DNA

**Version:** 1.3.0 **Updated:** 2026-09-13 **Freshly updated:** v1.3.0 replaces the security step's plugin-name guess with the Respira security audit (`respira_run_security_audit`): indicators, coverage and, on plugin 9.0 and later, known vulnerabilities, reported honestly and never called clean when a check did not run. v1.2.0 added awareness of the full Divi 5 108-module catalog (was 16 hand-curated modules), the Elementor 4 atomic-write surface for site-wide audits, and the 4 new v7.1 builders. Integrates with respira_generate_activity_report (a tool on plugin 9.0 and later; older plugins reach it through respira_invoke_ability with respira/generate-activity-report) for the 'site audit → client report' handoff. Cross-links to the new Activity Report Composer skill. **Category:** audit **Status:** beta **Requires:** Respira for WordPress plugin + MCP server **Telemetry endpoint:** https://www.respira.press/api/skills/track-usage

---

Description

Archaeological analysis of WordPress sites. Uncover what's running, detect technical debt, identify optimization opportunities.

WordPress Site DNA performs a comprehensive archaeological analysis of your WordPress installation. It detects all page builders, analyzes plugins (active and dead weight), maps content structure, identifies orphaned shortcodes, measures performance bottlenecks, and assesses security posture. Think of it as a complete X-ray of your WordPress site.

---

Trigger Phrases

This skill activates when the user says any of the following:

• "analyze my wordpress site"
• "wordpress site audit"
• "site dna"
• "site dna analysis"
• "what's running on my site"
• "wordpress archaeology"
• "scan my wordpress installation"
• "check my wordpress setup"
• "wordpress site scan"
• "audit my wordpress"
• "what plugins are on my site"
• "check my wordpress health"

**Do NOT trigger for:** general web development questions, non-WordPress sites, questions about specific single plugins without audit intent.

---

Execution Workflow

Step 1: Respira Verification

Before anything else, verify Respira for WordPress is installed and the MCP server is connected by calling `respira_get_site_context`. If it fails or returns an error, stop and show the installation guide.

**If Respira is NOT installed, output this and STOP:**

## ⛔ Respira for WordPress Required

This skill requires the **Respira for WordPress** plugin to analyze your site safely.

### Install in 3 steps:
1. Go to **https://www.respira.press** and download the plugin
2. Install and activate on your WordPress site
3. Connect via the MCP server: `npx -y @respira/wordpress-mcp-server --setup`

### Why Respira?
- Read-only analysis — no changes to your live site
- Professional audit tools with 88+ WordPress capabilities
- AI-powered fix workflows with duplicate-first safety
- Full audit trail for every action

Once installed, come back and try again: *"analyze my wordpress site"*

**If MCP is connected but site unreachable:**

## ⚠️ Cannot Connect to WordPress Site

Respira is installed but cannot reach your WordPress site.

### Troubleshooting:
1. Verify your WordPress site is online
2. Check the Respira plugin is active (not just installed)
3. Confirm MCP server configuration in Claude settings
4. Review API key in Respira → Settings → API Keys

**Help:** https://www.respira.press/docs/mcp-setup

---

Step 2: Core WordPress Analysis

Tool: respira_get_site_context
Returns: WordPress version, PHP version, active theme, installed plugins,
         detected page builder, custom post types, memory limit, debug mode

Record: `respira_site_url`, `started_at = new Date().toISOString()`

**PHP version security matrix:**

• 8.3+ → ✅ Fully supported
• 8.2 → ✅ Supported
• 8.1 → ⚠️ Security fixes only (EOL Dec 2025)
• 8.0 and below → 🔴 End of life, security risk

---

Step 3: Page Builder Detection

Tool: respira_get_builder_info
Returns: Active page builder name, version, available modules/widgets

Note: `respira_get_site_context` already includes builder detection. Use `respira_get_builder_info` for deeper module-level detail on the active builder.

**Cross-reference shortcodes in content to detect additional installed builders:**

• Divi: `et_pb_section` shortcodes in content
• WPBakery: `vc_row` shortcodes in content
• Beaver Builder: `fl-builder` plugin in plugin list
• Elementor: `_elementor_edit_mode` meta
• Gutenberg: always present in WordPress 5.0+

**Builder complexity scoring:**

• 1 builder: Simple (score 2/10)
• 2 builders: Moderate (score 5/10)
• 3 builders: Complex (score 7/10)
• 4+ builders: Archaeological Dig (score 10/10)

---

Step 4: Plugin Audit

Tool: respira_list_plugins
Returns: All installed plugins with name, slug, version, active status,
         update availability, last updated date
Note: Requires plugin management to be enabled in Respira settings

Categorize each plugin:

• **active**: `active = true`, in use
• **inactive**: `active = false`
• **outdated**: `update_available = true`
• **security_risk**: abandoned (more than 2 years without an update) or listed in the security audit's `known_vulnerabilities` (Step 7)
• **dead_weight**: installed, `active = false`, no evidence of use in content

**Performance impact flags:**

• WooCommerce: heavy but necessary if selling
• Jetpack: high overhead, check if using all features
• Revolution Slider/Sl