resonance-ops-page-audit

Audits live pages and sites from first principles and produces a ranked improvement backlog.

Updated Dec 1, 2025
One-click install
npx skills add https://github.com/manusco/wolfgang --skill resonance-ops-page-audit-manusco
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: resonance-ops-page-audit
Source: https://github.com/manusco/wolfgang/tree/main/.agents/skills/ops/page-audit
Command: npx skills add https://github.com/manusco/wolfgang --skill resonance-ops-page-audit-manusco

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Website and landing page reviews often stop at cosmetic tweaks or code-level bug hunts, missing whether each page actually does its job, delivers its value promise fast, and converts real users. This Skill runs a first-principles experience audit across a page or an entire site and turns the findings into a ranked, forward-looking improvement backlog. ## Core Features & Use Cases - First-Principles Page Interrogation: States each page's job in one sentence, measures the gap between the value promise and its delivery, and decides what to add, change, rearrange, or remove. - Orchestrated Lens Delegation: Coordinates specialized skills for copy, design, conversion, SEO, code audit, and QA instead of re-teaching each discipline, with a baseline pass from system health and code audit. - Forward Backlog Generation: Writes a FUTURE_IMPROVEMENTS.md per site, ranked by theme with effort, impact, and priority, plus a cross-site master report for multi-site runs. - Use Case: Point it at a running local build of your SaaS marketing site and receive a per-page findings sheet naming the single most important change per page, plus a prioritized backlog handed off for implementation. ## Quick Start Ask the agent to run /page-audit against your live URL or local site build to get a first-principles experience audit and a ranked FUTURE_IMPROVEMENTS.md backlog.

Frequently Asked Questions about resonance-ops-page-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit a landing page for conversion and UX?▼

Run /page-audit against a live URL or local build. It states the page's job in one sentence, measures the gap between the value promise and its delivery, checks clarity, CTA, design, function, and trust, then produces a ranked add/change/rearrange/remove findings sheet.

How to audit an entire website instead of a single page?▼

Invoke /page-audit on the whole site. It inventories every page and meaningful state from the routes and rendered output, runs system health and code audit as a baseline, interrogates each page, and writes a FUTURE_IMPROVEMENTS.md backlog per site.

Does the page audit implement or deploy the fixes it finds?▼

No. The audit only produces the findings sheet, plan, and forward backlog. Implementation is handed to /goal and deployment to /ship, keeping the audit focused on diagnosis rather than changes.

What happens if marketing claims on a page cannot be verified?▼

Unverifiable claims such as uptime or customer counts are flagged as trust risks, and the audit stops rather than optimizing conversion around a false promise. It still delivers findings on the verifiable parts like job, value gap, and action clarity.

Can this audit non-web products like apps or games?▼

Yes. The interrogation battery generalizes pages to screens and states, treating the core loop or aha moment as the value delivery and the path to first completed session as the conversion path. Each state is audited for its job, delivery, and next-move clarity.