CD xiaoyaoclaw-seo-skill
SEO analysis and optimization skill for websites. Use when auditing a site's search visibility, fixing rankings/traffic drops, optimizing pages for Google (Baidu/Bing) and AI search (ChatGPT/Perplexity/AI Overviews). Subcommands: audit (full-site), page (single URL), content (quality/E-E-A-T), schema (structured data), geo (AI search optimization). Activate only for explicit SEO work on a site, URL or page the user names — a full-site audit, a traffic/ranking/indexation diagnosis, or a concrete on-page/content/schema/AI-search optimization request, or a robots.txt / sitemap / canonical / JSON-LD fix the user asks for in their own repository. Do NOT activate for: general questions about SEO concepts ("what is SEO?"), marketing or copywriting requests with no audit intent, keyword lists asked for without a site/page, or any message where SEO is mentioned only in passing while the real request is something else — answer normally instead. 中文：网站搜索可见性分析与优化技能。当用户想优化网站搜索排名、做 SEO 审计、 诊断流量下降/排名消失、优化页面被 AI 搜索引用时使用。子命令：audit（全站审计）、 page（单页分析）、content（内容质量/E-E-A-T）、schema（结构化数据）、geo（AI搜索优化）。 仅当用户**指定了站点/URL/页面**并明确要做 SEO 相关操作时激活（全站体检、流量/排名/ 收录诊断、具体的页面/内容/结构化数据/AI 搜索优化，或要求修自家仓库的 robots.txt、 sitemap、canonical、JSON-LD）。**不激活**的场景：泛问概念（"SEO 是什么"）、 纯文案营销请求、没给站点的关键词清单、只是顺口提到 SEO 而真实诉求是别的事。 触发词（需与站点/URL 或明确诊断意图同时出现）：SEO、SEO审计、技术SEO、全站体检、 排名上不去、流量下降、不被收录、robots.txt、sitemap、canonical、 Core Web Vitals、LCP、H1、meta description、结构化数据、schema、JSON-LD、 富媒体摘要、AI搜索优化、AEO、GEO、llms.txt、E-E-A-T、关键词研究、内链。
SEO analysis and optimization skill for websites.
As a process D 40/100 · Unfinished process — References files that are not bundled: assets/examples/robots.txt.template
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The skill asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.
Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.
How to improve
- Shorten the description to 1024 characters.
- 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 · 1
✓ No critical or high findings
Medium and low: 1
-
medium Broad scope
meta-broad-allowed-toolsSKILL.md:1Broad tool permissions pre-approved: Bashallowed-tools: Read Write Edit Glob Grep Bash WebFetch WebSearch Browser
Files scanned: 14. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- error
description-longdescription is 1496 chars, limit 1024 - warning
missing-refreference to a missing file: assets/examples/robots.txt.template
Process rating: all ten parameters 40/100
- 0Tools and files. 1 referenced file(s) missing: assets/examples/robots.txt.template
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 50Failures and branches. 0 branches, has a failure section
- 100Steps. 77 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2098 tokens
- 100Running it twice. No mutating operations
- low 11 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 1495: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- -229 emoji in the instructions: noise for the model
- +2Single-language instructions
- +5Description quotes 2 example trigger phrases
- +4Structure: 24 headings
- +3Step-by-step instructions: 77 items
- +4Reference files are cited in the instructions (5 of 5)
- +3All 1 scripts are documented
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 57.