CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

seo-page-builder

用于创建、审计或优化 SEO 工具页、AI generator/remover/enhancer/converter/editor 功能页、feature page JSON、工具页 on-page SEO brief,以及 App Router/i18n 功能页路由。

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./templates/skills/seo-page-builder/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 well-structured, lean operational playbook: a bounded scope statement, a 10-step execution order with measured validation gates, a concrete input/deliverable contract, and clean progressive disclosure into four references and a real audit script. Remaining gains are small: trim the provenance note, show one complete example invocation (including the required --phrase flag), and make the QA fix-and-retry loop explicit.

DimensionReasoningScore

Conciseness

The body is dense and imperative, assumes competence (no explanation of what SEO or Firecrawl is), and nearly every line carries executable instruction — matching 'efficient; minor instances of over-explanation that could be trimmed'. The main trim candidates are the provenance/licensing blockquote ("本技能改编自 yuzeiki 的...") and a few editorial asides, which keep it from the 'every token earns its place' 5 anchor.

4 / 5

Actionability

Concrete, executable guidance throughout: named MCP tools (firecrawl_search/scrape/map/interact), script invocations with flags (`scripts/onpage-audit.py --suggest/--benchmark/--targets`, verified against the actual script), a specific input checklist, and a concrete deliverables list. It stays at 4 because `--benchmark` actually requires `--phrase` (the script errors without it) and no full example invocation with arguments is shown, leaving minor gaps versus copy-paste-ready.

4 / 5

Workflow Clarity

The 10-step 执行顺序 is clearly sequenced with strong validation gates ('先拿到密度区间再动笔', '禁止让模型编 PAA', step 10 measures the delivered page and writes metrics into QA), matching 'clear sequence with most checkpoints present'. It falls short of 5 because the fix-and-retry feedback loop on QA failure is implicit — no explicit 'if the audit fails, fix and re-run' instruction.

4 / 5

Progressive Disclosure

A clear overview with well-signaled one-level-deep references: the 参考资料 section lists every reference and script with a one-line description, inline pointers appear at the point of use (step 1, 3, 6), all referenced files exist in the bundle, and the references cross-reference only peers with no deeper nesting. This matches the 'clear overview with well-signaled one-level-deep references; easy navigation' anchor, and re-reading the 4 anchor confirms the structure exceeds 'minor organization gaps'.

5 / 5

Total

17

/

20

Passed

Description

66%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.

The description is specific and distinctive, clearly naming the artifact types (feature pages, tool-page JSON, SEO briefs, App Router/i18n routing) and three concrete operations. Its main weakness is the missing 'when to use' guidance — no explicit trigger clause — which is the rubric's heaviest-weighted dimension. Adding a 'Use when...' sentence with natural trigger phrases would lift it substantially.

Suggestions

Append an explicit trigger clause to the description, e.g. '当用户提到 add feature page、new generator/tool page、feature page JSON、AI 工具页 SEO 或工具页 route 接线时使用' — this directly addresses the completeness cap.

Surface 2-3 natural English/Chinese trigger phrases users would actually say (e.g. 'new tool page', '工具页文案') in the description itself rather than only in the body's 适用场景 section.

Briefly delimit scope in the description (e.g. '不处理博客或普通营销落地页') to reduce overlap risk with general SEO and i18n/routing skills.

DimensionReasoningScore

Specificity

Three concrete verbs ("创建、审计或优化") are applied to a specific enumerated artifact set ("AI generator/remover/enhancer/converter/editor 功能页", "feature page JSON", "工具页 on-page SEO brief", "App Router/i18n 功能页路由"), matching the 'several specific actions; minor gaps' anchor. It falls short of the 5 anchor because the verb set is small and '优化' is broad compared to a comprehensive list of distinct concrete actions.

4 / 5

Completeness

The 'what' is clear (create, audit, or optimize the enumerated tool-page artifacts), but the description contains no 'Use when...' clause or any equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. The trigger scenarios exist only in the body's 适用场景 section, not in the description.

3 / 5

Trigger Term Quality

The description includes natural terms users would say — "generator", "remover", "enhancer", "converter", "editor", "feature page JSON", "on-page SEO brief" — giving good keyword coverage with synonyms across tool types. It stays at 4 rather than 5 because common natural phrasings a user might actually say (e.g. 'new tool page', 'add a page', 'page SEO') appear only partially or not at all.

4 / 5

Distinctiveness Conflict Risk

A clear niche (tool-type SEO pages, feature page JSON, App Router/i18n feature-page routing) with distinct trigger terms keeps overlap risk minor, matching the 'mostly distinct' anchor. It is not 5 because the description itself does not delimit scope (exclusions live in the body) and 'App Router/i18n 功能页路由' could pull in generic routing or i18n requests that belong to other skills.

4 / 5

Total

15

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository

fengshao1227/ccg-workflow

Path

templates/skills/seo-page-builder/SKILL.md

Reviewed

Table of Contents

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.