audit website for SEO, security, performance and 200+ other issues
v1.0.4Audit websites for SEO, performance, security, technical, content, and 15 other issue cateories with 230+ rules using the squirrelscan CLI. Returns LLM-optimized reports with health scores, broken links, meta tag analysis, and actionable recommendations. Use to discover and asses website or webapp issues and health.
⭐ 1· 1.8k·1 current·1 all-time
by@nc9
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description map directly to the instructions: the SKILL.md calls the squirrel CLI (squirrel audit, report, init) and links to squirrelscan.com/docs. Requiring the CLI in PATH is expected for this functionality and no unrelated credentials or services are requested.
Instruction Scope
Instructions focus on crawling, analyzing, and reporting via the squirrel CLI. They instruct creating a local squirrel.toml and using cached project DBs and may suggest piping output to an LLM (e.g., 'squirrel audit ... --format llm | claude'). This is appropriate for the purpose, but piping audit output to external LLMs may expose site content — users should be aware of data flow.
Install Mechanism
There is no install spec in the skill bundle (instruction-only). The skill expects the user to install the squirrel CLI from the project's site; nothing in the skill tries to download or execute code itself.
Credentials
The skill requests no environment variables, credentials, or config paths outside its project config (squirrel.toml). That aligns with its purpose; no unrelated secrets are requested.
Persistence & Privilege
Skill is not always-enabled and does not request elevated or persistent platform privileges. It reads/writes local project config and caches per the CLI's normal operation, which is expected for a CLI-based auditor.
Assessment
This skill is an instruction-only wrapper for the squirrel CLI and appears coherent. Before installing/using: (1) install the squirrel CLI from the official site and verify its binary provenance; (2) be aware audits crawl live sites and can affect site performance — prefer staging for intrusive deep scans; (3) the CLI will create/modify a local squirrel.toml and cache a project DB in your working directory — run it in an appropriate folder and review created files; (4) avoid piping sensitive site data to external LLMs or untrusted endpoints (e.g., piping to a remote model could expose site content or secrets); (5) check the project license and docs linked in the SKILL.md. If you need the agent to avoid reading local files or external model calls, restrict its allowed tools or run audits manually.Like a lobster shell, security has layers — review code before you run it.
latestvk97bnt8qa16ryydzxcvjshvp7980ta64
License
MIT-0
Free to use, modify, and redistribute. No attribution required.