菜单
Audit websites for SEO, technical, content, and security issues using squirrelscan CLI. Returns LLM-optimized reports with health scores, broken links, meta tag analysis, and actionable recommendations. Use when analyzing websites, debugging SEO issues, or checking site health.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Create distinctive, production-grade frontend interfaces with high design quality. Generates creative, polished code that avoids generic AI aesthetics. Use when the user asks to build web components, pages, artifacts, posters, or applications, or when any design skill requires project context.
Svelte 5 runes guidance. Use for reactive state, props, effects, or Svelte 4→5 migration. Covers $state, $derived, $effect, $props, $bindable. Prevents mixing syntaxes and reactivity mistakes.
SvelteKit data flow guidance. Use for load functions, form actions, and server/client data. Covers +page.server.ts vs +page.ts, serialization, fail(), redirect(), error().
SvelteKit remote functions guidance. Use for command(), query(), form() patterns in .remote.ts files.
SvelteKit structure guidance. Use for routing, layouts, error handling, SSR, or svelte:boundary. Covers file naming, nested layouts, error boundaries, pending UI, and hydration.
TypeScript functional programming. Use for pure functions, immutability, composition. Favors ternaries, switch, map/filter/reduce over imperative code. Concise, declarative patterns.
| name | audit-website |
| description | Audit websites for SEO, technical, content, and security issues using squirrelscan CLI. Returns LLM-optimized reports with health scores, broken links, meta tag analysis, and actionable recommendations. Use when analyzing websites, debugging SEO issues, or checking site health. |
| license | See LICENSE file in repository root |
| compatibility | Requires squirrel CLI installed and accessible in PATH |
| metadata | {"author":"squirrelscan","version":"1.7"} |
| allowed-tools | Bash(squirrel:*) |
Audit websites for SEO, technical, content, performance and security issues using the squirrelscan cli.
squirrelscan provides a cli tool squirrel - available for macos, windows and linux. It carries out extensive website auditing by emulating a browser, search crawler, and analyzing the website's structure and content against over 140+ rules.
It will provide you a list of issues as well as suggestions on how to fix them.
You can look up the docs for any rule with this template:
https://docs.squirrelscan.com/rules/{rule_category}/{rule_id}
example:
https://docs.squirrelscan.com/rules/links/external-links
This skill enables AI agents to audit websites for over 140 rules in 20 categories, including:
and more!
The audit crawls the website, analyzes each page against audit rules, and returns a comprehensive report with:
Use this skill when you need to:
This skill requires the squirrel CLI to be installed and available in your PATH.
If squirrel is not already installed, you can install it using:
curl -fsSL https://squirrelscan.com/install | bash
This will:
~/.local/share/squirrel/releases/{version}/~/.local/bin/squirrel~/.squirrel/settings.jsonIf ~/.local/bin is not in your PATH, add it to your shell configuration:
export PATH="$HOME/.local/bin:$PATH"
Install using PowerShell:
irm https://squirrelscan.com/install.ps1 | iex
This will:
%LOCALAPPDATA%\squirrel\If using Command Prompt, you may need to restart your terminal for PATH changes to take effect.
Check that squirrel is installed and accessible:
squirrel --version
Running squirrel init will setup a squirrel.toml file for configuration in the current directory.
Each project should have a squirrel project name for the database - by default this is the name of the website you audit - but you can set it yourself so that you can place all audits for a project in one database
You do this either on init with:
squirrel init --project-name my-project
or config:
squirrel config set project.name my-project
The project name is used to identify the project in the database and is used to generate the database name.
It is stored in ~/.squirrel/projects/
There are three processes that you can run and they're all cached in the local project database:
the 'audit' command is a wrapper around these three processes and runs them sequentially:
squirrel audit https://example.com --format llm
YOU SHOULD always prefer format option llm - it was made for you and provides an exhaustive and compact output format.
If the user doesn't provide a website to audit - extrapolate the possibilities in the local directory and checking environment variables (ie. linked vercel projects, references in memory or the code).
If the directory you're running for provides for a method to run or restart a local dev server - run the audit against that.
If you have more than one option on a website to audit that you discover - prompt the user to choose which one to audit.
If there is no website - either local, or on the web to discover to audit, then ask the user which URL they would like to audit.
You should PREFER to audit live websites - only there do we get a TRUE representation of the website and performance or rendering issuers.
If you have both local and live websites to audit, prompt the user to choose which one to audit and SUGGEST they choose live.
You can apply fixes from an audit on the live site against the local code.
The audit process is two steps:
# Step 1: Run audit (default: console output)
squirrel audit https://example.com
# Step 2: Export as LLM format
squirrel report <audit-id> --format llm
Audit more pages:
squirrel audit https://example.com --max-pages 200
Force fresh crawl (ignore cache):
squirrel audit https://example.com --refresh
Resume interrupted crawl:
squirrel audit https://example.com --resume
Verbose output for debugging:
squirrel audit https://example.com --verbose
| Option | Alias | Description | Default |
|---|---|---|---|
--format <fmt> | -f <fmt> | Output format: console, text, json, html, markdown, llm | console |
--max-pages <n> | -m <n> | Maximum pages to crawl (max 500) | 500 |
--refresh | -r | Ignore cache, fetch all pages fresh | false |
--resume | - | Resume interrupted crawl | false |
--verbose | -v | Verbose output | false |
--debug | - | Debug logging | false |
| Option | Alias | Description |
|---|---|---|
--format <fmt> | -f <fmt> | Output format: console, text, json, html, markdown, xml, llm |
The audit command shows human-readable console output by default with colored output and progress indicators.
To get LLM-optimized output, use the report command with --format llm:
squirrel report <audit-id> --format llm
The LLM format is a compact XML/text hybrid optimized for token efficiency (40% smaller than verbose XML):
See OUTPUT-FORMAT.md for detailed format specification.
# User asks: "Check squirrelscan.com for SEO issues"
squirrel audit https://squirrelscan.com --format llm
# User asks: "Do a thorough audit of my blog with up to 500 pages"
squirrel audit https://myblog.com --max-pages 500 --format llm
# User asks: "Re-audit the site and ignore cached results"
squirrel audit https://example.com --refresh --format llm
# First run an audit
squirrel audit https://example.com
# Note the audit ID from output (e.g., "a1b2c3d4")
# Later, export in different format
squirrel report a1b2c3d4 --format llm
If you see this error, squirrel is not installed or not in your PATH.
Solution:
curl -fsSL https://squirrelscan.com/install | bashexport PATH="$HOME/.local/bin:$PATH"squirrel --versionIf squirrel is not executable:
chmod +x ~/.local/bin/squirrel
For very large sites, the audit may take several minutes. Use --verbose to see progress:
squirrel audit https://example.com --format llm --verbose
Ensure the URL includes the protocol (http:// or https://):
# ✗ Wrong
squirrel audit example.com
# ✓ Correct
squirrel audit https://example.com
The audit is stored in a local database and can be retrieved later with squirrel report commands.
squirrel audit --help