BF gingiris-seo-geo-agent
You know SEO matters but you don't have time to do daily audits, track rankings, or validate schema markup. This is the AI agent SOP — set it up once, let your coding agent run it daily on autopilot. What's inside: • Daily 4-phase audit automation (technical → content → performance → report) • GSC data pipeline (pull, analyze, prioritize keywords automatically) • AI traffic tracking (ChatGPT/Perplexity referrals in GA4) • Schema validation + auto-fix workflows • IndexNow integration for instant indexing on publish • Week 0-4 ramp-up timeline (from zero to ~32K impressions) Built from: Designed for Claude Code / OpenClaw / Cursor autonomous execution. Validated with real content site data. Triggers: "SEO agent" | "SEO automation" | "SEO Agent SOP" | "autonomous SEO" | "SEO daily report" | "SEO Agent运营" | "SEO自动化" | "GEO agent" | "32K impressions" | "3.2万曝光" | "keyword mapping" | "CTA conversion SOP" | "SEO报告模板" | "IndexNow setup" | "AI crawler robots.txt" | "DataForSEO" | "SEO工具链" | "SEO Agent 日报"
As a process F 31/100 · Will not run — References files that are not bundled: references/full-sop.md, [CTA_URL]?utm_source=blog&utm_medium=organic&utm_campaign=seo-[slug]
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
missing-refreference to a missing file: references/full-sop.md - warning
missing-refreference to a missing file: [CTA_URL]?utm_source=blog&utm_medium=organic&utm_campaign=seo-[slug] - note
frontmatter-keyunknown frontmatter key "source"
Process rating: all ten parameters 31/100
- 0Tools and files. 2 referenced file(s) missing: references/full-sop.md, [CTA_URL]?utm_source=blog&utm_medium=organic&utm_campaign=seo-[slug]
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 40Consistency. Frontmatter name (gingiris-seo-geo-agent) differs from the folder (gr-seo-geo-agent)
- 100Steps. 34 steps
- 100Execution cost. Instruction body is 983 tokens
- 100Running it twice. No mutating operations
- low 10 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +4Description does not say when NOT to use the skill (false activations)
- +3Description length 1014: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +5Description quotes 18 example trigger phrases
- +4Structure: 17 headings
- +3Step-by-step instructions: 34 items
- +4Has examples (3 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 64.