Awesome-omni-skills seo-v2

SEO: Universal SEO Analysis Skill workflow skill. Use this skill when the user needs Run a broad SEO audit across technical SEO, on-page SEO, schema, sitemaps, content quality, AI search readiness, and GEO. Use as the umbrella skill when the user asks for a full SEO analysis or strategy and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

install

source · Clone the upstream repo

git clone https://github.com/diegosouzapw/awesome-omni-skills

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/diegosouzapw/awesome-omni-skills "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/seo-v2" ~/.claude/skills/diegosouzapw-awesome-omni-skills-seo-v2 && rm -rf "$T"

manifest: skills/seo-v2/SKILL.md

SEO: Universal SEO Analysis Skill

Overview

This public intake copy packages

plugins/antigravity-awesome-skills-claude/skills/seo

from

https://github.com/sickn33/antigravity-awesome-skills

into the native Omni Skills editorial shape without hiding its origin.

Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow.

This intake keeps the copied upstream files intact and uses

metadata.json

plus

ORIGIN.md

as the provenance anchor for review.

SEO: Universal SEO Analysis Skill Comprehensive SEO analysis across all industries (SaaS, local services, e-commerce, publishers, agencies). Orchestrates 12 specialized sub-skills and 7 subagents (+ optional extension sub-skills like seo-dataforseo).

Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: Orchestration Logic, Industry Detection, Quality Gates, Scoring Methodology, Sub-Skills, Subagents.

When to Use This Skill

Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request.

Use when the user asks for a full SEO audit or broad SEO strategy.
Use as the umbrella entry point when multiple SEO dimensions are in scope.
Use when the task spans technical SEO, content, schema, sitemaps, and AI search readiness together.
Use when the request clearly matches the imported source intent: Run a broad SEO audit across technical SEO, on-page SEO, schema, sitemaps, content quality, AI search readiness, and GEO. Use as the umbrella skill when the user asks for a full SEO analysis or strategy.
Use when the operator should preserve upstream workflow detail instead of rewriting the process from scratch.
Use when provenance needs to stay visible in the answer, PR, or review packet.

Operating Table

Situation	Start here	Why it matters
First-time use	`metadata.json`	Confirms repository, branch, commit, and imported path before touching the copied workflow
Provenance review	`ORIGIN.md`	Gives reviewers a plain-language audit trail for the imported source
Workflow execution	`references/cwv-thresholds.md`	Starts with the smallest copied file that materially changes execution
Supporting context	`references/eeat-framework.md`	Adds the next most relevant copied source file without loading the entire package
Handoff decision	`## Related Skills`	Helps the operator switch to a stronger native skill when the task drifts

Workflow

This workflow is intentionally editorial and operational at the same time. It keeps the imported source useful to the operator while still satisfying the public intake standards that feed the downstream enhancer flow.

Confirm the user goal, the scope of the imported workflow, and whether this skill is still the right router for the task.
Read the overview and provenance files before loading any copied upstream support files.
Load only the references, examples, prompts, or scripts that materially change the outcome for the current request.
Execute the upstream workflow while keeping provenance and source boundaries explicit in the working notes.
Validate the result against the upstream expectations and the evidence you can point to in the copied files.
Escalate or hand off to a related skill when the work moves out of this imported workflow's center of gravity.
Before merge or closure, record what was used, what changed, and what the reviewer still needs to verify.

Imported Workflow Notes

Imported: Orchestration Logic

When the user invokes

/seo audit

, delegate to subagents in parallel:

Detect business type (SaaS, local, ecommerce, publisher, agency, other)
Spawn subagents: seo-technical, seo-content, seo-schema, seo-sitemap, seo-performance, seo-visual, seo-geo
Collect results and generate unified report with SEO Health Score (0-100)
Create prioritized action plan (Critical -> High -> Medium -> Low)

For individual commands, load the relevant sub-skill directly.

Examples

Example 1: Ask for the upstream workflow directly

Use @seo-v2 to handle <task>. Start from the copied upstream workflow, load only the files that change the outcome, and keep provenance visible in the answer.

Explanation: This is the safest starting point when the operator needs the imported workflow, but not the entire repository.

Example 2: Ask for a provenance-grounded review

Review @seo-v2 against metadata.json and ORIGIN.md, then explain which copied upstream files you would load first and why.

Explanation: Use this before review or troubleshooting when you need a precise, auditable explanation of origin and file selection.

Example 3: Narrow the copied support files before execution

Use @seo-v2 for <task>. Load only the copied references, examples, or scripts that change the outcome, and name the files explicitly before proceeding.

Explanation: This keeps the skill aligned with progressive disclosure instead of loading the whole copied package by default.

Example 4: Build a reviewer packet

Review @seo-v2 using the copied upstream files plus provenance, then summarize any gaps before merge.

Explanation: This is useful when the PR is waiting for human review and you want a repeatable audit packet.

Best Practices

Treat the generated public skill as a reviewable packaging layer around the upstream repository. The goal is to keep provenance explicit and load only the copied source material that materially improves execution.

Keep the imported skill grounded in the upstream repository; do not invent steps that the source material cannot support.
Prefer the smallest useful set of support files so the workflow stays auditable and fast to review.
Keep provenance, source commit, and imported file paths visible in notes and PR descriptions.
Point directly at the copied upstream files that justify the workflow instead of relying on generic review boilerplate.
Treat generated examples as scaffolding; adapt them to the concrete task before execution.
Route to a stronger native skill when architecture, debugging, design, or security concerns become dominant.

Troubleshooting

Problem: The operator skipped the imported context and answered too generically

Symptoms: The result ignores the upstream workflow in

plugins/antigravity-awesome-skills-claude/skills/seo

, fails to mention provenance, or does not use any copied source files at all. Solution: Re-open

metadata.json

ORIGIN.md

, and the most relevant copied upstream files. Load only the files that materially change the answer, then restate the provenance before continuing.

Problem: The imported workflow feels incomplete during review

Symptoms: Reviewers can see the generated

SKILL.md

, but they cannot quickly tell which references, examples, or scripts matter for the current task. Solution: Point at the exact copied references, examples, scripts, or assets that justify the path you took. If the gap is still real, record it in the PR instead of hiding it.

Problem: The task drifted into a different specialization

Symptoms: The imported skill starts in the right place, but the work turns into debugging, architecture, design, security, or release orchestration that a native skill handles better. Solution: Use the related skills section to hand off deliberately. Keep the imported provenance visible so the next skill inherits the right context instead of starting blind.

Related Skills

```
@00-andruia-consultant-v2
```
- Use when the work is better handled by that native specialization after this imported skill establishes context.
```
@10-andruia-skill-smith-v2
```
- Use when the work is better handled by that native specialization after this imported skill establishes context.
```
@20-andruia-niche-intelligence-v2
```
- Use when the work is better handled by that native specialization after this imported skill establishes context.
```
@2d-games
```
- Use when the work is better handled by that native specialization after this imported skill establishes context.

Additional Resources

Use this support matrix and the linked files below as the operator packet for this imported skill. They should reflect real copied source material, not generic scaffolding.

Resource family	What it gives the reviewer	Example path
`references`	copied reference notes, guides, or background material from upstream	`references/cwv-thresholds.md`
`examples`	worked examples or reusable prompts copied from upstream	`examples/n/a`
`scripts`	upstream helper scripts that change execution or validation	`scripts/n/a`
`agents`	routing or delegation notes that are genuinely part of the imported package	`agents/n/a`
`assets`	supporting assets or schemas copied from the source package	`assets/n/a`

Imported Reference Notes

Imported: Quick Reference

Command	What it does
`/seo audit <url>`	Full website audit with parallel subagent delegation
`/seo page <url>`	Deep single-page analysis
`/seo sitemap <url or generate>`	Analyze or generate XML sitemaps
`/seo schema <url>`	Detect, validate, and generate Schema.org markup
`/seo images <url>`	Image optimization analysis
`/seo technical <url>`	Technical SEO audit (9 categories)
`/seo content <url>`	E-E-A-T and content quality analysis
`/seo geo <url>`	AI Overviews / Generative Engine Optimization
`/seo plan <business-type>`	Strategic SEO planning
`/seo programmatic [url\|plan]`	Programmatic SEO analysis and planning
`/seo competitor-pages [url\|generate]`	Competitor comparison page generation
`/seo hreflang [url]`	Hreflang/i18n SEO audit and generation
`/seo dataforseo [command]`	Live SEO data via DataForSEO (extension)
`/seo image-gen [use-case] <description>`	AI image generation for SEO assets (extension)

Imported: Reference Files

Load these on-demand as needed (do NOT load all at startup):

```
references/cwv-thresholds.md
```
: Current Core Web Vitals thresholds and measurement details
```
references/schema-types.md
```
: All supported schema types with deprecation status
```
references/eeat-framework.md
```
: E-E-A-T evaluation criteria (Sept 2025 QRG update)
```
references/quality-gates.md
```
: Content length minimums, uniqueness thresholds

Imported: Industry Detection

Detect business type from homepage signals:

SaaS: pricing page, /features, /integrations, /docs, "free trial", "sign up"
Local Service: phone number, address, service area, "serving [city]", Google Maps embed
E-commerce: /products, /collections, /cart, "add to cart", product schema
Publisher: /blog, /articles, /topics, article schema, author pages, publication dates
Agency: /case-studies, /portfolio, /industries, "our work", client logos

Imported: Quality Gates

Read

references/quality-gates.md

for thin content thresholds per page type. Hard rules:

WARNING at 30+ location pages (enforce 60%+ unique content)
HARD STOP at 50+ location pages (require user justification)
Never recommend HowTo schema (deprecated Sept 2023)
FAQ schema for Google rich results: only government and healthcare sites (Aug 2023 restriction); existing FAQPage on commercial sites -> flag Info priority (not Critical), noting AI/LLM citation benefit; adding new FAQPage -> not recommended for Google benefit
All Core Web Vitals references use INP, never FID

Imported: Scoring Methodology

SEO Health Score (0-100)

Weighted aggregate of all categories:

Category	Weight
Technical SEO	22%
Content Quality	23%
On-Page SEO	20%
Schema / Structured Data	10%
Performance (CWV)	10%
AI Search Readiness	10%
Images	5%

Priority Levels

Critical: Blocks indexing or causes penalties (immediate fix required)
High: Significantly impacts rankings (fix within 1 week)
Medium: Optimization opportunity (fix within 1 month)
Low: Nice to have (backlog)

Imported: Sub-Skills

This skill orchestrates 12 specialized sub-skills (+ 2 extensions):

seo-audit -- Full website audit with parallel delegation
seo-page -- Deep single-page analysis
seo-technical -- Technical SEO (9 categories)
seo-content -- E-E-A-T and content quality
seo-schema -- Schema markup detection and generation
seo-images -- Image optimization
seo-sitemap -- Sitemap analysis and generation
seo-geo -- AI Overviews / GEO optimization
seo-plan -- Strategic planning with templates
seo-programmatic -- Programmatic SEO analysis and planning
seo-competitor-pages -- Competitor comparison page generation
seo-hreflang -- Hreflang/i18n SEO audit and generation
seo-dataforseo -- Live SEO data via DataForSEO MCP (extension)
seo-image-gen -- AI image generation for SEO assets via Gemini (extension)

Imported: Subagents

For parallel analysis during audits:

```
seo-technical
```
-- Crawlability, indexability, security, CWV
```
seo-content
```
-- E-E-A-T, readability, thin content
```
seo-schema
```
-- Detection, validation, generation
```
seo-sitemap
```
-- Structure, coverage, quality gates
```
seo-performance
```
-- Core Web Vitals measurement
```
seo-visual
```
-- Screenshots, mobile testing, above-fold
```
seo-geo
```
-- AI crawler access, llms.txt, citability, brand mention signals
```
seo-dataforseo
```
-- Live SERP, keyword, backlink, local SEO data (extension, optional)
```
seo-image-gen
```
-- SEO image audit and generation plan (extension, optional)

Imported: Error Handling

Scenario	Action
Unrecognized command	List available commands from the Quick Reference table. Suggest the closest matching command.
URL unreachable	Report the error and suggest the user verify the URL. Do not attempt to guess site content.
Sub-skill fails during audit	Report partial results from successful sub-skills. Clearly note which sub-skill failed and why. Suggest re-running the failed sub-skill individually.
Ambiguous business type detection	Present the top two detected types with supporting signals. Ask the user to confirm before proceeding with industry-specific recommendations.

Imported: Limitations

Use this skill only when the task clearly matches the scope described above.
Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.