plugins/seo/skills/seo-orchestrator/SKILL.md
Routes SEO requests to the correct specialist skill based on intent. Use when user asks for general SEO help, a full audit, or when the specific SEO discipline is unclear. Trigger phrases: 'SEO', 'optimize for search', 'SEO audit', 'search engine optimization'. Routes to 12 specialist skills covering on-page, technical, schema, images, sitemaps, i18n, keywords, links, competitors, programmatic, AI search, and app store optimization.
npx skillsauth add petrogurcak/skills seo-orchestratorInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Entry point for all SEO work. Identifies the right specialist skill based on what the user is trying to do.
If you already know which discipline you need, call the specialist skill directly:
/seo:on-page-seo — title tags, H1, keyword density, E-E-A-T, entity SEO/seo:technical-seo — Core Web Vitals, crawlability, robots.txt, security headers/seo:schema-markup — JSON-LD, rich results, video schema, validation/seo:image-seo — AVIF/WebP, LCP images, alt text, Google Lens/seo:sitemap-management — XML sitemaps, IndexNow, crawl budget/seo:hreflang-i18n — international SEO, hreflang tags, country targeting/seo:keyword-research — search volume, keyword difficulty, intent mapping/seo:link-building — backlinks, outreach, linkable assets/seo:competitor-pages — X vs Y pages, alternatives pages/seo:programmatic-seo — database-driven pages, pSEO infrastructure/seo:ai-ready — llms.txt, AI crawlers, GEO, AI Overviews/seo:aso-optimization — App Store, Google Play, keyword optimizationMatch the user's words to the right skill:
| Trigger keywords | Skill |
|---|---|
| "on-page", "title tag", "meta description", "H1", "keyword density", "E-E-A-T", "content optimization", "entity SEO" | on-page-seo |
| "technical", "core web vitals", "performance", "crawl", "robots.txt", "page speed", "security headers", "canonical" | technical-seo |
| "schema", "structured data", "JSON-LD", "rich results", "video schema", "markup validation" | schema-markup |
| "image", "lazy loading", "WebP", "AVIF", "alt text", "compression", "Google Lens", "OG image" | image-seo |
| "sitemap", "IndexNow", "crawl budget", "indexing issues", "XML sitemap" | sitemap-management |
| "hreflang", "international", "i18n", "multilingual", "localization", "multi-language", "country targeting" | hreflang-i18n |
| "keyword", "search volume", "keyword difficulty", "intent", "keyword gap" | keyword-research |
| "link building", "backlinks", "outreach", "domain authority", "linkable assets" | link-building |
| "competitor", "vs", "comparison", "alternative", "X vs Y" | competitor-pages |
| "programmatic", "pSEO", "database pages", "at scale" | programmatic-seo |
| "AI search", "llms.txt", "AI crawlers", "GEO", "AI Overviews", "ChatGPT traffic" | ai-ready |
| "app store", "ASO", "Play Store", "App Store", "mobile app ranking" | aso-optimization |
If the request matches multiple skills, ask the user which aspect they want to tackle first, or use Full Audit Mode.
When the user says "full SEO audit", "complete SEO review", or "audit my site", run skills in this order:
technical-seo — Foundation first. Fix crawlability and Core Web Vitals before anything else.on-page-seo — Content and entity optimization per page.schema-markup — Structured data implementation and validation.image-seo — Image formats, loading strategy, alt text.sitemap-management — Sitemap health, IndexNow, crawl budget.link-building — Authority gaps and outreach opportunities.Present findings from each skill before moving to the next. Summarize critical issues (P0) separately at the end.
| Skill | Discipline | One-line description |
|---|---|---|
| on-page-seo | On-page | Optimizes title tags, H1, keyword usage, E-E-A-T, and entity authority per page |
| technical-seo | Technical | Audits Core Web Vitals, crawlability, robots.txt, canonicals, and security headers |
| schema-markup | Structured data | Implements JSON-LD for rich results, video schema, and AI entity understanding |
| image-seo | Images | Selects formats (AVIF/WebP), optimizes LCP images, alt text, and visual search |
| sitemap-management | Indexing | Creates and monitors XML sitemaps, implements IndexNow, manages crawl budget |
| hreflang-i18n | International | Sets up hreflang tags, audits i18n errors, guides country targeting strategy |
| keyword-research | Keywords | Finds keywords by search volume, difficulty, and intent for content planning |
| link-building | Authority | Builds backlinks through linkable assets, broken link building, and outreach |
| competitor-pages | Competitor content | Creates X vs Y and alternatives pages with conversion optimization |
| programmatic-seo | Scale | Builds database-driven page templates for high-volume keyword coverage |
| ai-ready | AI search | Optimizes for AI Overviews, llms.txt, GEO, and AI crawler accessibility |
| aso-optimization | App stores | Optimizes App Store and Google Play listings for keyword ranking and conversion |
development
Builds a pre-launch social proof strategy through structured beta programs using D'Souza Brain Audit interviews. Use when launching new products/services and need compelling testimonials, planning a beta cohort, designing interview questions to harvest objection-busting social proof, improving video testimonials for landing pages, or designing case studies with metrics. Trigger phrases include "beta tester program for testimonials", "pre-launch social proof", "Brain Audit testimonial framework", "case study harvest", "reverse testimonial", "video testimonial mechanics", "social proof landing page", "sběr referencí", "beta tester program", "testimonial pro landing page", "social proof před launchem", "rozhovor s klientem", "case study sběr", "reference před spuštěním". NOT for ongoing case study production (use growth-hacking case-study approach), offer design (use offer-creation), or conversion optimization (use ux-optimization).
development
Use when planning a product launch and the product type is unclear or could be either generic (SaaS/app/physical) or info-product. Routes between marketing:launch-strategy (generic launches) and marketing:info-product-launch (courses, memberships, ebooks, cohorts, communities). Trigger phrases - "launch", "spuštění", "go-to-market", "product launch", "release strategy", "uvedení na trh", "launch plan", "spuštění produktu", "launch sequence", "launch strategy". Do NOT trigger when product type is already clear (use specific skill directly).
testing
Specialized 8-week launch cadence for info-products — online courses, cohort programs, memberships, communities, ebooks, masterminds. Combines Jeff Walker's Product Launch Formula (Seed/Internal/JV variants, PLC sequence, open-cart day-by-day) with Stu McLaren's membership mechanics (closed cart, Success Path) and Hormozi Grand Slam Offer stacking. Use when planning "launch online kurzu", "info-product launch", "PLF launch", "course launch", "membership launch", "cohort launch", "ebook launch", "open cart close cart", "8-week launch of online course", "beta cohort to launch sequence", "spuštění kurzu", "launch členské sekce", "open cart strategie". Differentiates from marketing:launch-strategy (generic SaaS/app launches) — info-product-specific. NOT for SaaS launches, physical products, or services.
development
Use when releasing an Expo/React Native mobile app to App Store and Google Play - covers eas submit, ASC "Submit for Review", Play promote Internal→Production, OTA update, and decoding common silent failures (Apple agreement expiry, missing English locale, Background Location declaration, web bundle failure on react-native-maps).