Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

wp-report

Estrellas1

Forks0

Actualizado15 de junio de 2026 a las 21:29

Generate self-contained HTML or plain-text audit reports from WP-Arsenal JSON output. Combines results from multiple scripts into one colour-coded report. Use after any audit run to produce a shareable deliverable for clients or records.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

rahlplx

rahlplx/wp-arsenal

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Desarrolladores de softwareOcupaciones informáticas y matemáticas·SOC 15-1252

SKILL.md

readonly

name	wp-report
description	Generate self-contained HTML or plain-text audit reports from WP-Arsenal JSON output. Combines results from multiple scripts into one colour-coded report. Use after any audit run to produce a shareable deliverable for clients or records.
triggers	["generate report","create report","HTML report","audit report","security report","export findings"]

Skill: wp-report

Converts the JSON output from any WP-Arsenal script into a clean, self-contained HTML report — one file, no internet required, safe to email or archive.

Workflow

# Step 1 — run scripts with --json flag
python scripts/security/wp-scan.py       --config config/config.yaml --json > logs/scan.json
python scripts/security/wp-deep-audit.py --config config/config.yaml --json > logs/deep-audit.json
python scripts/forensics/wp-db-audit.py  --config config/config.yaml --json > logs/db-audit.json

# Step 2 — combine into one HTML report
python scripts/management/wp-report.py \
    --input logs/scan.json logs/deep-audit.json logs/db-audit.json \
    --output reports/site-audit-2026-06-16.html \
    --site-label "example.com — June 2026"

Usage

# Single file → HTML report
python scripts/management/wp-report.py \
    --input logs/scan.json \
    --output reports/scan.html

# All JSON files in a directory → one combined report
python scripts/management/wp-report.py \
    --input-dir logs/weekly/ \
    --output reports/weekly-summary.html \
    --site-label "Weekly sweep — 2026-06-16"

# Plain text (for terminal, plain-text email, or log archiving)
python scripts/management/wp-report.py \
    --input logs/scan.json \
    --format text

# Print to stdout (no --output = stdout)
python scripts/management/wp-report.py \
    --input logs/deep-audit.json \
    --format text | mail -s "Site audit" client@example.com

Report contents

Severity summary cards (CRITICAL / HIGH / MEDIUM / LOW / INFO counts)
Per-script sections — findings table with severity badge, category, detail, path
Stats table — script-specific counters (files scanned, plugins checked, etc.)
Self-contained HTML — works offline, safe to attach to emails

Common patterns

Full incident audit report

# Run all scripts
for script in wp-forensics wp-deep-audit wp-db-audit wp-attacker-profile; do
    python scripts/forensics/${script}.py --config config/config.yaml --json \
        > logs/${script}-$(date +%Y%m%d).json
done

# Generate report
python scripts/management/wp-report.py \
    --input-dir logs/ \
    --output reports/incident-report-$(date +%Y%m%d).html \
    --site-label "Incident Report — $(date +%Y-%m-%d)"

Client-ready report after cleanup

python scripts/security/wp-scan.py --config config/config.yaml --json > logs/post-cleanup-scan.json
python scripts/management/wp-report.py \
    --input logs/post-cleanup-scan.json \
    --output "reports/Clean Bill of Health — $(date +%Y-%m-%d).html" \
    --site-label "Post-cleanup verification"

Más de este repositorio

mismo repositorio

wp-ci-deploy

rahlplx/wp-arsenal

Deploy a theme, plugin, or wp-content subset to a WordPress server from a CI/CD pipeline, with automatic pre-deploy backup, post-deploy health check, and automatic rollback on failure. Designed for GitHub Actions, GitLab CI, or any pipeline that can run Python.

2026-06-161

wp-woo-audit

rahlplx/wp-arsenal

Security and integrity audit for WooCommerce stores. Checks REST API key scope, payment gateway exposure, webhook HTTPS enforcement, suspicious $0 orders, exposed wc-logs (PII/payment data), and coupon abuse.

2026-06-161

wp-child-theme

rahlplx/wp-arsenal

Scaffold and deploy a WordPress child theme via SSH. Generates style.css, functions.php (with correct parent style enqueueing), and index.php. Supports Kadence, Astra, GeneratePress, Hello Elementor, OceanWP, and any custom parent. Can activate the child theme immediately after creation.

2026-06-161

wp-theme-switch

rahlplx/wp-arsenal

Safely switch WordPress themes via SSH with automatic rollback if the site goes down. Records the previous theme for instant rollback. Verifies HTTP 200 before and after the switch.

2026-06-161

wp-theme-audit

rahlplx/wp-arsenal

Security audit of WordPress themes via SSH. Scans for PHP malware patterns, injected scripts, recently modified files, and unexpected file types. Also checks DB for customizer injections and Elementor postmeta payloads. Use after any attack or before going live with a new/inherited theme.

2026-06-161

elementor-guide

rahlplx/wp-arsenal

Comprehensive guide to building, maintaining, and recovering Elementor-based WordPress sites. Covers the CSS pipeline, global styles (Kit), common post-attack failures and fixes, Pro vs Free features, and integration with Kadence and Hello Elementor themes.

2026-06-161

Skill: wp-report

Converts the JSON output from any WP-Arsenal script into a clean, self-contained HTML report — one file, no internet required, safe to email or archive.

Workflow

# Step 1 — run scripts with --json flag python scripts/security/wp-scan.py --config config/config.yaml --json > logs/scan.json python scripts/security/wp-deep-audit.py --config config/config.yaml --json > logs/deep-audit.json python scripts/forensics/wp-db-audit.py --config config/config.yaml --json > logs/db-audit.json # Step 2 — combine into one HTML report python scripts/management/wp-report.py \ --input logs/scan.json logs/deep-audit.json logs/db-audit.json \ --output reports/site-audit-2026-06-16.html \ --site-label "example.com — June 2026"

Usage

# Single file → HTML report python scripts/management/wp-report.py \ --input logs/scan.json \ --output reports/scan.html # All JSON files in a directory → one combined report python scripts/management/wp-report.py \ --input-dir logs/weekly/ \ --output reports/weekly-summary.html \ --site-label "Weekly sweep — 2026-06-16" # Plain text (for terminal, plain-text email, or log archiving) python scripts/management/wp-report.py \ --input logs/scan.json \ --format text # Print to stdout (no --output = stdout) python scripts/management/wp-report.py \ --input logs/deep-audit.json \ --format text | mail -s "Site audit" client@example.com

Report contents

Severity summary cards (CRITICAL / HIGH / MEDIUM / LOW / INFO counts)

Per-script sections — findings table with severity badge, category, detail, path

Stats table — script-specific counters (files scanned, plugins checked, etc.)

Self-contained HTML — works offline, safe to attach to emails

Common patterns

Full incident audit report

# Run all scripts for script in wp-forensics wp-deep-audit wp-db-audit wp-attacker-profile; do python scripts/forensics/${script}.py --config config/config.yaml --json \ > logs/${script}-$(date +%Y%m%d).json done # Generate report python scripts/management/wp-report.py \ --input-dir logs/ \ --output reports/incident-report-$(date +%Y%m%d).html \ --site-label "Incident Report — $(date +%Y-%m-%d)"

Client-ready report after cleanup

python scripts/security/wp-scan.py --config config/config.yaml --json > logs/post-cleanup-scan.json python scripts/management/wp-report.py \ --input logs/post-cleanup-scan.json \ --output "reports/Clean Bill of Health — $(date +%Y-%m-%d).html" \ --site-label "Post-cleanup verification"