Agents / Skills
Skillskills/openrush-site-audit/SKILL.md

Site Audit

Run a focused, credit-conscious OpenRush technical site audit. Use when a user asks for a technical SEO audit, crawl or site-health review, weak-page review, prioritized technical fixes, or a monthly technical check for a domain.

Agents that use this skill

2 items

Complete source

Copy and paste SKILL.md

skills/openrush-site-audit/SKILL.md
---
name: openrush-site-audit
description: Run a focused, credit-conscious OpenRush technical site audit. Use when a user asks for a technical SEO audit, crawl or site-health review, weak-page review, prioritized technical fixes, or a monthly technical check for a domain.
---

# OpenRush Site Audit

## Before the Audit

Confirm OpenRush MCP is available and call `describe_capabilities` first. If it is unavailable, use `openrush-seo-agent-setup` to connect it.

Ask for the domain, target market and language, priority pages or products, and whether the user wants a quick or deeper review. Say that deeper analysis can use more credits.

## Workflow

1. Call `inspect_domain` to establish the domain context.
2. Call `audit_site` for technical findings.
3. Use `inspect_page` only for a small shortlist of pages where it will change the recommendation. Ask before many page drilldowns.

Prefer the two broad calls over a large number of narrow calls.

## Report

Return a short, prioritized plan:

1. Top fixes, ordered by likely impact and effort.
2. Weak pages or sections to review, only when supported by the response.
3. What coverage was assessed and what was not.
4. What to re-check next month.

Use `coverage`, `facts[*].provenance`, `resources`, and `next_actions` from the OpenRush response. Separate source facts from recommendations. Never invent crawl findings, traffic, rankings, page performance, or audit metrics.

## Monthly Prompt

```md
Monthly site audit:
Use OpenRush to audit {domain}. Focus on technical issues that could affect organic growth. Return the top fixes and what to re-check next month.
```

## Shared OpenRush References

Read [credits and rate limits](../../lib/CREDITS-AND-RATE-LIMITS.md) before paid work, the [tool reference](../../lib/TOOLS.md) before selecting a tool, [error handling](../../lib/ERRORS.md) for any MCP error, and the [Open Fact Envelope](../../lib/OPEN-FACT-ENVELOPE.md) before interpreting results. A `402` is a hard stop: tell the user to top up at `https://www.openrush.com/dashboard` and make no further OpenRush MCP calls.