oegeyilmaz9/seo-aeo-geo-ultimate / skills/seo
seo
VerifiedThe autonomous front door and end-to-end orchestrator for SEO, AEO, GEO, AI search, keyword research and LLM-friendly Markdown discovery. Screen all 27 skills, execute applicable workflows, maintain public content maps and private Markdown work documents, and deliver one evidence-linked result to the authorized boundary without ranking or citation guarantees.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 15.3 KB |
| agents/openai.yaml | config | 630 B |
| references/autonomous-orchestration-contract.md | markdown | 9.4 KB |
| references/contracts/action-plan.schema.json | config | 10.2 KB |
| references/contracts/contracts-lock.json | config | 5.4 KB |
| references/contracts/evidence-record.schema.json | config | 1.7 KB |
| references/contracts/optimization-brief.schema.json | config | 6.3 KB |
| references/contracts/platform-controls.schema.json | config | 6.6 KB |
| references/contracts/provider-operation-receipt.schema.json | config | 6.5 KB |
| references/contracts/query-corpus.schema.json | config | 6.0 KB |
| references/contracts/research-pack.schema.json | config | 5.2 KB |
| references/contracts/seo-findings.schema.json | config | 5.2 KB |
| references/contracts/seo-performance-run.schema.json | config | 7.6 KB |
| references/contracts/site-graph.schema.json | config | 4.3 KB |
| references/contracts/visibility-run.schema.json | config | 13.8 KB |
| references/decision-and-release-contract.md | markdown | 2.6 KB |
| references/markdown-delivery-contract.md | markdown | 4.3 KB |
| references/routing-matrix.md | markdown | 9.7 KB |
references/markdown-delivery-contract.md
View on GitHub# Markdown delivery: seo
Every material work step has a substantive Markdown document and a direct link in private `index.md`. Include outcome/status, scope, evidence dates/links, facts vs inferences, decisions, limitations, owner and next destination. Drafts remain draft/provisional until their owning semantic validator passes. Use the suite artifact renderer for validated formal bundles; do not replace immutable JSON, CSV, raw captures or schema.
Lane documents: `index.md; delivery-summary.md`.
Own the public Markdown inventory, the work index, exact direct destinations and all lane handoffs. Require seo-sitemap, seo-architecture, seo-content and seo-technical for a public Markdown corpus; run seo-research for keyword ownership. Screen all 27 skills; do not run irrelevant verticals. Close only after applicable documents and checks resolve.
## Public knowledge profile
For authorized public-site implementation, require lowercase `/llms.txt`, `/sitemap.md`, topic maps and substantive `.md` equivalents for every eligible canonical page in the declared scope. These are owner-defined delivery requirements, not universal SEO/AEO/GEO platform requirements. robots.txt, XML sitemaps, feeds, schema and protocol files keep their native formats. One-page or answer-only work stays bounded and records its work note without changing the whole site.
Use reviewed content from the same revision as HTML. Preserve facts, citations, dates, units, locale, media meaning and public access policy. Private reports, analytics, credentials, admin URLs, personalized content and paywalled material never become public mirrors. Every excluded/unknown inventory URL has a private disposition; unknown eligibility or a partial inventory prevents a whole-site-complete claim.
Direct destinations must actually resolve; planned URLs are labelled planned. Verify links, map coverage, source hashes, public output hashes, editorial parity, UTF-8 MIME delivery, cache/deletion refresh, maintenance owner and the chosen canonical/indexing policy. Public Markdown is a content representation, not a crawler permission, schema replacement or evidence that an engine retrieves/cites it.
Native entry points also carry concise navigation hints: robots `#` comments, XML sitemap/index comments, and two reader-facing sentences in llms.txt direct an interested LLM to the actual Markdown map and answer. Preserve all existing crawl rules and native sitemap elements; comments are discovery hints with no guaranteed consumer. The technical/sitemap owners verify protocol invariance, real destinations and delivered comment retention. Read the full contract's “Native entry-point navigation hints” section before editing those sources.
## Shared tools and full contract
Resolve `<suite-root>` from `.seo-suite-runtime.json` beside SKILL.md in Codex, `${CLAUDE_PLUGIN_ROOT}` in Claude Code, or the absolute suite checkout. Read `<suite-root>/docs/MARKDOWN-DISCOVERY.md` before corpus generation/publication. It owns the detailed inventory, routing, native-format exceptions, privacy, acceptance and source-review rules; do not improvise a conflicting contract.
- Public export: `python "<suite-root>/scripts/manage_markdown_site.py" build --inventory <private/inventory.json> --output <new-public-candidate>`.
- Local projection: `python "<suite-root>/scripts/manage_markdown_site.py" validate --manifest <private-manifest.json> --root <public-candidate>`.
- Full live delivery after authorized publication: same tool, `live --manifest ... --root ... --report <private/live-verification.md>`. A failed/rate-limited run is incomplete, never retried in a loop.
- Work index: `python "<suite-root>/scripts/manage_markdown_work.py" --root <private-work> init --title "Work title"`; use `add --id <step-id> --path <step.md> --title "Step title" --status <draft|provisional|completed|blocked|not-applicable> --owner "Owner" --outcome "Actual result"`, then `check --final` before complete closeout. Equivalent maintained tooling is acceptable when these invariants are verified.
The deterministic export verifies parity with supplied reviewed Markdown, not editorial truth or live HTML. Formal AEO/GEO claims still require the pinned Research Pack. Owner-required source navigation/parity work can proceed locally without inventing engine observations. Preserve separate local acceptance, live delivery and provider outcome states.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |