site-audit

Audit key website pages and generate a prioritized issue report.

Updated Mar 12, 2026
One-click install
npx skills add https://github.com/BeanMap/roasters-hub --skill site-audit-beanmap
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: site-audit
Source: https://github.com/BeanMap/roasters-hub/tree/main/.claude/skills/site-audit
Command: npx skills add https://github.com/BeanMap/roasters-hub --skill site-audit-beanmap

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates a comprehensive website audit by visiting key pages, capturing console logs, network issues, user flows and SEO signals, and generating a prioritized report to guide fixes before release.

Core Features & Use Cases

  • Automated page audits: navigates critical routes, collects logs, screenshots, and accessibility data for P1 pages and P2 pages.
  • Issue aggregation: compiles a structured list of problems with severity levels (CRITICAL / HIGH / MEDIUM / LOW / GAPS) for roadmap planning.
  • Deterministic workflows: uses Playwright MCP to ensure repeatable checks across environments.
  • Use Case: run audits before merging to ensure design and functionality quality across homepage, roasters, map, and registration forms.

Quick Start

Run the site-audit skill against your base URL to generate a report at .tmp/audit-YYYY-MM-DD.md

Frequently Asked Questions about site-audit

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

FAQPage Schema
How do I automate a website audit using Playwright to capture console logs and network requests?

Automate your website audit by running the site-audit skill, which uses Playwright MCP to navigate critical routes, capture console logs, network issues, and multi-viewport screenshots to produce a structured findings report.

What is the best way to run a visual QA pass before merging to catch UI and UX issues?

A visual QA pass before merging is best handled by systematically auditing key pages using Playwright to capture multi-viewport screenshots and aggregate issues into a prioritized report for release readiness.

Does the Playwright MCP website audit generate a structured report with issue severity levels?

Yes, the Playwright MCP website audit compiles a structured list of problems with severity levels ranging from CRITICAL to LOW and GAPS, outputting a deterministic audit file for roadmap planning.

Can I run a website audit against a specific base URL to check critical user flows like registration and dashboards?

Yes, you can run the website audit against an optional base URL argument to functionally test critical user flows including registration, sign-in, and dashboards, producing a prioritized markdown report.

How do I ensure repeatable website checks across different environments when auditing for bugs?

Repeatable website checks across environments are achieved by using deterministic workflows powered by Playwright MCP, ensuring consistent capture of browser logs, network requests, and screenshots during every audit.