CLANKER.NET
GENERAL squirrelscan/skills

Audit a Website and Fix It

Audit a website with the squirrelscan CLI and fix the findings in code. Runs SEO, performance, security, technical, content, accessibility, and 15 other rule categories (260+ rules), returns an LLM-optimized report, then drives an iterative fix loop, mapping issues to source files, applying fixes, and re-auditing until the site scores well. Use to discover and assess website or webapp issues and drive them to fixed.

GENERAL
USE THIS SKILL

DOWNLOAD THE APP TO INSTALL AND USE /squirrelscan__audit-website ON YOUR DEVICE

Scan to open on your device
QR code for Audit a Website and Fix It Opens skill content in Expo Go
COMMAND
/squirrelscan__audit-website
CATEGORY
General
REPOSITORY
squirrelscan/skills
COMMIT

SKILL PROMPT

--- name: audit-website description: Audit a website with the squirrelscan CLI and fix the findings in code. Runs SEO, performance, security, technical, content, accessibility, and 15 other rule categories (260+ rules), returns an LLM-optimized report, then drives an iterative fix loop, mapping issues to source files, applying fixes, and re-auditing until the site scores well. Use to discover and assess website or webapp issues and drive them to fixed. license: See LICENSE file in repository root compatibility: Requires squirrel CLI installed and accessible in PATH metadata: author: squirrelscan version: "2.0" allowed-tools: Bash(squirrel:*) Read Edit Grep Glob --- # Audit a Website and Fix It Run a squirrelscan audit against a website, read the LLM report, map each issue to the code or content that causes it, fix in batches, and re-audit until the score target is met. Requires the `squirrel` CLI ([squirrelscan.com/download](https://squirrelscan.com/download); verify with `squirrel --version`). For CLI setup, login, publishing, MCP, and general CLI usage, use the companion `squirrelscan` skill. ## Rule docs Look up any rule at `https://docs.squirrelscan.com/rules/{rule_category}/{rule_id}`, for example: https://docs.squirrelscan.com/rules/links/external-links ## Running the audit ```bash squirrel audit https://example.com --format llm ``` - ALWAYS use `--format llm`: it is compact, exhaustive, and made for agents. - If the user doesn't provide a URL, ask which site to audit. - PREFER auditing the live site: only there do you see true rendering, performance, and redirect behavior. If both a local dev server and a live site exist, suggest the live one; apply the fixes to the local code either way. - Audits are cached locally. Re-render later without recrawling: `squirrel report <audit-id> --format llm`. ### Scan progression 1. **First pass, quick coverage** (the default): a fast, shallow scan to learn the site's structure, technology, and biggest proble [... prompt truncated for preview ...]