skillZs
★ LIVE SKILL TAGS ★
>>> LIVE SKILLS INDEX <<<
* OPEN SOURCE *
NO LOGIN, NO TRACKING
※ REAL INSTALL DATA ※
← back to all skills
hainrixz/claude-seo-ai187 installs

audit

Audit a website or web codebase for SEO and AI-search (GEO/AEO) — produces two independent 0-100 scores (Search SEO + AI Visibility) plus a prioritized, evidence-backed report persisted on disk. Read-only; never writes to the project. Use when the user asks to audit, analyze, check, or score a site's SEO, structured data/schema, meta tags, Core Web Vitals, robots.txt, sitemaps, or AI discovery files, or how it ranks in Google and is cited by AI engines (ChatGPT, Perplexity, Google AI Overviews, Gemini, Claude).

How do I install this agent skill?

npx skills add https://github.com/hainrixz/claude-seo-ai --skill audit
view source ↗

Is this agent skill safe to install?

  • Gen Agent Trust Hubpass

    The skill performs SEO audits by fetching content from URLs and reading local files. It is vulnerable to indirect prompt injection as it lacks boundary markers or sanitization for the untrusted data it processes using tools like Bash.

  • Socketpass

    No alerts

  • Snykwarn

    Risk: MEDIUM · 1 issue

What does this agent skill do?

/claude-seo-ai:audit

A full, read-only SEO + AI-search audit. Never writes to the user's project; artifacts go to ${CLAUDE_PLUGIN_DATA}/runs (or --out).

$ARGUMENTS = <url|path> [flags]. The target is a URL (https://…) or a local web project / built HTML. If no target is given, ask for one. Flags are forwarded verbatim to the orchestrator, which passes them to audit.mjs: --pages N (pages to sample, default 12) · --max N (URLs to consider, default 40) · --render static|auto|js (default static — a headless run never launches a browser unless asked) · --ua default|googlebot|bingbot|gptbot|oai-searchbot|claude-searchbot (or a literal UA string) · --vertical <ids> (comma list of saas,blog-publisher,local-business,ecommerce,docs,generic; omit it to let the run infer one) · --environment production|preview|staging|local · --feed <path> (a product feed for the ACP lint) · --out <dir> (runs root; defaults to ${CLAUDE_PLUGIN_DATA}/runs).

What to do

  1. Invoke the seo-orchestrator skill with the target and all flags. It runs audit.mjs once — acquisition (crawl/snapshot → PageSnapshot v2), platform profile, vertical guess and the whole deterministic checks registry in a single call — refines the vertical with seo-vertical-detect (references/routing.md), dispatches the read-only specialist subagents in parallel with a dispatch envelope, then merges everything back with report.mjs --merge and scores.
  2. Present, from report.json:
    • The two scores — Search SEO and AI Visibility — each with a band (A–F) and a one-line interpretation. Never blended.
    • A per-category breakdown for each score; coverage mode (full vs deterministic-only), the data tier reached, and the needs_api / manual_review counts (score confidence).
    • The sampling table: pages crawled by role, templates discovered vs sampled, and every skip with its reason.
    • The platform profile (platform/framework/plugins, environment — e.g. "noindex expected on preview").
    • A prioritized action list sorted by impact ÷ effort: status, evidence, recommendation, fixability (auto/proposed/advisory), expected_impact (axis + confidence + magnitude).
    • The absolute report path (<run_dir>/report.md).
  3. End by offering: "Run /claude-seo-ai:fix <target> to apply the safe, deterministic fixes — you'll confirm each change" and "/claude-seo-ai:compare --baseline latest --against <target> after you deploy".

Every finding conforms to schema/finding.schema.json with reproducible evidence. Respond in the user's language (EN/ES).

How can the creator link this skill?

Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.

<a href="https://skillzs.dev/skills/hainrixz/claude-seo-ai/audit">View audit on skillZs</a>