ericrisco/rsc-harness / skills/seo-geo
seo-geo
VerifiedUse when one existing page needs to rank in Google AND get cited by AI answer engines — auditing a URL for on-page SEO, structured-data JSON-LD, GEO citation levers, Core Web Vitals, crawlability, and AI-bot access in robots.txt. NOT writing the article body (that is `article-writing`), NOT keyword research or content strategy (that is `content-engine`).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 11.1 KB |
| evals/README.md | markdown | 1.0 KB |
| evals/cases.yaml | config | 3.7 KB |
| references/ai-crawler-control.md | markdown | 3.6 KB |
| references/schema-recipes.md | markdown | 4.3 KB |
| scripts/verify.shexecutable | script | 9.1 KB |
evals/README.md
View on GitHub# Evals — seo-geo
`cases.yaml` drives two kinds of check. The `should_trigger` / `should_not_trigger`
prompts are routing assertions: run them through the repo's eval harness against this
skill's `description` + triggers and confirm the router selects `seo-geo` for the trigger
set (including the non-obvious GPTBot/robots and dead-FAQ-schema cases and the
Spanish/Catalan prompts) and prefers the named sibling for each near-miss
(`content-engine`, `article-writing`, `performance`, `nextjs`, `accessibility`). The
`capability` case is graded manually or by an LLM judge against its `must_include` rubric:
feed the scenario to an agent loaded with this skill and check the produced audit hits
every rubric line (length-bounded title/meta, answer-first note, valid Article JSON-LD
with no dead type, ≥2 Princeton GEO levers, CWV stated at p75 with a performance handoff,
the AI-bot/robots note, and an explicit handoff statement). There is no automated scorer
in this folder; routing is harness-run, capability is rubric-judged.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |