AD website-leadgen
网站获客（CRO/转化漏斗）审计与优化 skill。当用户提供一个网址，希望对站点做获客体检、按「流量入口→Landing Page→产品页面→CTA→Contact→Form→提交→Thank You→Lead」转化漏斗逐维度分析页面与获客表单（普通表单与询盘表单）、提出 5 个优化点并在用户同意后通过建站 MCP 工具落地低风险优化时使用。内置零依赖 Python 审计脚本，输出结构化报告与按风险分级的优化建议。
网站获客（CRO/转化漏斗）审计与优化 skill。当用户提供一个网址，希望对站点做获客体检、按「流量入口→Landing Page→产品页面→CTA→Contact→Form→提交→Thank You→Lead」转化漏斗逐维度分析页面与获客表单（普通表单与询盘表单）、提出 5 个优化点并在用户同意后通过建站…
As a process D 41/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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: 8. 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") - note
frontmatter-keyunknown frontmatter key "id" - note
frontmatter-keyunknown frontmatter key "display_name" - note
frontmatter-keyunknown frontmatter key "display_name_en" - note
frontmatter-keyunknown frontmatter key "description_zh" - note
frontmatter-keyunknown frontmatter key "description_en" - note
frontmatter-keyunknown frontmatter key "agent_created"
Process rating: all ten parameters 41/100
- 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 (website-leadgen) differs from the folder (yunzhi-website-leadgen)
- 60Tools and files. Uses tools (python) that frontmatter does not declare
- 100Steps. 54 steps
- 100Execution cost. Instruction body is 2020 tokens
- 100Running it twice. No mutating operations
- low The response is described with custom markup (4 tags): a typed call is more reliable
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
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 210: enough signal without eating the budget
- +4Structure: 13 headings
- +3Step-by-step instructions: 54 items
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (5 of 5)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 76.