aios-audit

Runs URL SEO audits via the audit engine and interprets grounded findings from findings.json.

1|Updated Jul 8, 2026
One-click install
npx skills add https://github.com/codesofadan/danyals-aios --skill aios-audit-codesofadan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: aios-audit
Source: https://github.com/codesofadan/danyals-aios/tree/main/.claude/skills/aios-audit
Command: npx skills add https://github.com/codesofadan/danyals-aios --skill aios-audit-codesofadan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Running an SEO audit involves orchestrating an external audit engine, respecting tier and permission gates, polling for completion, and interpreting raw findings without inventing metrics. This Skill manages that entire workflow so operators get accurate, grounded audit results without manual API calls or misreported scores. ## Core Features & Use Cases - Audit Orchestration: Creates Free or Paid audit runs via POST /audits, polls to a terminal state, and pulls findings.json and report.pdf artifacts. - Tier and Permission Gating: Enforces the run_audits permission, rejects paid audit types on the Free tier, and surfaces SSRF guard rejections instead of retrying. - Grounded Interpretation: Ranks findings by severity then lowest per-check score, flags confidence below 0.6 as needing validation, and routes data gaps to humans rather than fabricating metrics. - Use Case: An operator says "audit this client's site" — the Skill reads the audit board and KPIs, creates the run, waits for completion, and returns the composite score with the top five grounded findings. ## Quick Start Ask the assistant to run an SEO audit on a client URL, for example: run a Free audit of https://example.com for client Acme and show me the top findings.

Frequently Asked Questions about aios-audit

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

FAQPage Schema
How do I run an SEO audit on a URL with this Skill?▼

Provide the client name or id, the public target URL, and optionally a tier (Free or Paid) and audit types. The Skill creates the run via POST /audits, polls until done or failed, then pulls findings.json and reports the composite score and top findings.

What is the difference between Free and Paid audit tiers?▼

Free runs only the deterministic onpage and technical dimensions with zero paid-provider spend. Paid unlocks offpage, local, geo, and strategy types but spends metered audit-provider budget, so switching to Paid requires explicit operator confirmation.

Why does creating an audit return a 403 error?▼

A 403 from POST /audits means the caller lacks the run_audits permission. Read operations like viewing the audit board and stats only need view_reports, but creating runs is restricted to provisioned staff.

Can I audit an internal or private IP address?▼

No. The endpoint runs an SSRF guard that rejects private or internal addresses with a 400 error. The Skill surfaces that reason and stops rather than retrying with an internal host.

What happens when paid audit provider keys are dormant?▼

The engine degrades to its deterministic subset instead of running live paid checks. The Skill labels the result as degraded and not a live Paid audit, and never presents the degraded numbers as real paid-provider data.

How are low-confidence audit findings handled?▼

Any finding with confidence below 0.6 is marked as needing validation rather than presented as settled. Findings containing data gaps or [NEEDS: ...] markers are routed to a human and never filled in by the Skill.