seo

SEO 增长引擎。GSC 分析、关键词研究、标题优化、多语言翻译、内链策略、技术审计。当用户提到 SEO、CTR、曝光、踩词、优化标题、搜索排名、GSC、内链、写博客、翻译文章时路由到此。

Quality

65%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./templates/skills/domains/seo/SKILL.md

Quality

Content

40%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a clean, token-efficient index, but it indexes nothing: the referenced `seo-growth.md` does not exist, no executable guidance is present, and the multi-step workflow exists only as an unlabeled arrow chain with no validation for its batch operations. The skill's real content is missing entirely.

Suggestions

Create `seo-growth.md` (under `references/` or alongside the index) containing the actual full-cycle workflow, or inline the workflow steps directly into SKILL.md.

Replace the arrow chain with numbered steps that include executable commands and an explicit validation checkpoint after the batch translation step (e.g., verify rendered pages/translations before deployment).

Drop the 触发关键词 section or fold it into the description — it duplicates the frontmatter triggers without adding guidance.

Dimension	Reasoning	Score
Conciseness	The body is lean with zero over-explanation — every line is a capability table row or a trigger term. Not 5 because the 触发关键词 section duplicates the frontmatter description's trigger list, spending tokens without adding guidance.	4 / 5
Actionability	The body only describes: a table naming "全周期 SEO 工作流" with an arrow chain (GSC 诊断 → … → 部署) and no commands, code, or concrete steps. The one pointer, `seo-growth.md`, does not exist in any bundle directory, so even the hint resolves to nothing. Not 1 because the file pointer and staged sequence at least hint at where work happens.	2 / 5
Workflow Clarity	A rough sequence is present in the arrow chain but every step is undefined and no validation checkpoints exist, while the skill involves batch operations (批量翻译, 部署) that the rubric says require feedback loops. This is the 'rough sequence, poorly defined, validation absent' anchor; not 3 because even a single detailed step or check is missing.	2 / 5
Progressive Disclosure	Structure is nominally fine — a short index signaling one reference one level deep — but the referenced `seo-growth.md` is absent (no references/, scripts/, or assets/ directories exist), so navigation is broken and the skill body contains none of the actual workflow content. This lands at 'minimal structure' rather than the well-organized 4-5 anchors whose references resolve.	2 / 5
	Total	10 / 20 Passed

Description

91%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: concise, bilingual, with an explicit routing clause and concrete capability list. Its only weaknesses are minor — generic phrasing on the technical-audit capability and trigger terms broad enough to occasionally overlap with general writing/translation skills.

Suggestions

Add English trigger terms that appear in the body (Search Console, keywords, seoTitle, meta description, internal linking) to the description so it covers users who ask in English, not just Chinese.

Make 技术审计 concrete (e.g., which checks or signals it audits) so every listed capability is equally specific.

Dimension	Reasoning	Score
Specificity	Names six concrete capabilities ("GSC 分析、关键词研究、标题优化、多语言翻译、内链策略、技术审计"), matching the 'lists several specific actions; minor gaps' anchor. Not 5 because terms like 技术审计 are generic and the actions give no hint of method or tooling; not 3 because the coverage goes well beyond 1-2 actions.	4 / 5
Completeness	Explicitly answers both: the 'what' via the capability list and the 'when' via "当用户提到…时路由到此" with concrete trigger phrases, mirroring the 'Use when the user mentions…' pattern in the 5 anchor. Not 4, since the when-clause is already explicit and trigger-specific.	5 / 5
Trigger Term Quality	Comprehensive natural trigger coverage in both languages — "SEO、CTR、曝光、踩词、优化标题、搜索排名、GSC、内链、写博客、翻译文章" — including colloquial synonyms like 踩词 that users would actually say. Missing nothing material; clearly the top anchor.	5 / 5
Distinctiveness Conflict Risk	A clear SEO/GSC niche with distinct triggers, but the broad 写博客 and 翻译文章 triggers create minor overlap risk with general writing and translation skills. Mostly distinct rather than the minimal-conflict 5 anchor.	4 / 5
	Total	18 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: fengshao1227/ccg-workflow
Path: templates/skills/domains/seo/SKILL.md
Commit: f349e3d

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.