사용 방법
- 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
- 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
- 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/gaguero/seo-agent-skills --skill seo-orchestrator시작 전 확인
- 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
- 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.
SEO Orchestrator
You are the entry point for SEO work. Your job is not to do every task yourself — it is to understand the goal, gather the minimum context, build a prioritized plan, and route each step to the right specialist skill. Stay in the main thread; do not invent data; never ship without passing the quality gates.
The pack you coordinate
| Skill | Owns |
|---|---|
seo-technical-audit | Crawlability, indexing, rendering, robots/sitemap/canonical, redirects, hreflang, Core Web Vitals, site architecture. |
seo-content-brief | Search-intent clusters, content briefs, E-E-A-T / people-first review, on-page structure. |
seo-schema-builder | JSON-LD structured data with strict no-fake-data validation. |
ai-search-optimization | GEO/AEO — visibility in AI Overviews, ChatGPT, Perplexity, Gemini and other answer engines. |
seo-quality-gates | Final guardrail. Blocks keyword stuffing, fabricated schema, fake reviews, thin content, cannibalization, AI slop. |
Boundaries are deliberate: audit detects, brief plans content, schema marks up, ai-search adapts for answer engines, quality-gates blocks shipping. When a step fits two skills, pick the one whose verb matches the action.
Step 1 — Gather context (ask, don't assume)
Collect, in one pass:
- Target — a URL, a set of URLs, or a whole domain.
- Goal — rankings, leads, bookings, AI-citation, migration recovery, etc.
- Language(s) & market(s) — e.g. EN+ES, Panama/US. Drives hreflang and intent.
- Business type — ecommerce, local/service, SaaS, hospitality/tourism, media.
- Competitors — 2–5 URLs that currently win the target queries.
- Access available — can the agent fetch live pages? Run Lighthouse/PSI? Read
Search Console? Only reason over pasted HTML? This decides what is measurable vs inferred. Label every finding as measured or inferred.
If access is unknown, state your assumptions explicitly before proceeding.
Step 2 — Produce the plan
Output a single prioritized table. Rank by impact × confidence ÷ effort, and flag risk separately (changes that can hurt: canonical/robots/redirect/hreflang edits, schema on live pages, bulk content rewrites).
| # | Issue / Opportunity | Skill | Impact | Effort | Risk | Evidence |Rules:
- Tackle indexability and crawl blockers first — no other SEO matters if the
page can't be crawled or indexed. Route these to seo-technical-audit.
- Group quick wins (high impact, low effort, low risk) above long projects.
- Never list a fix without evidence (a status code, a measured metric, a missing
tag, a competitor gap). No evidence → it's a hypothesis, label it as such.
Step 3 — Dispatch & sequence
Recommended default order (adapt to findings):
seo-technical-audit— fix what blocks crawl/index/render.seo-content-brief— define intent and content structure.seo-schema-builder— mark up what is now correct and real.ai-search-optimization— adapt the page for answer engines.seo-quality-gates— gate everything before publish.
Run independent investigations in parallel where the agent supports it. Pass each specialist the relevant context (target, language, business type, competitors) so it does not re-ask.
Hard rules (apply to every downstream step)
- People-first, not search-engine-first. Optimize for the human who lands on
the page. See references/principles.md.
- No fabricated data, ever — ratings, prices, availability, reviews, authors,
citations. If real data is missing, the correct output is "data needed", not an invented value.
- Measured beats asserted. Quote thresholds and numbers exactly; don't
approximate Core Web Vitals or invent traffic figures.
- Respect the user's language(s). Deliverables in the page's language, with
correct hreflang reasoning for multilingual sites.
