BC geo-rank-architect
GEO搜索占位架构师——AI搜索时代品牌霸屏利器,5维GEO评分+JSON-LD注入+评分门控,提升AI搜索引擎引用率。核心能力: JSON-LD结构化数据注入 功能涵盖: rank, a。Use when 需要SEO优化、关键词分析、排名提升、搜索流量优化时使用。不适用于黑帽SEO手段。适用于独立开发者、企业团队和自动化工作流场景。 功能涵盖: architect。
GEO搜索占位架构师——AI搜索时代品牌霸屏利器,5维GEO评分+JSON-LD注入+评分门控,提升AI搜索引擎引用率。核心能力: JSON-LD结构化数据注入 功能涵盖: rank, a。Use when…
As a process C 53/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- 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
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: All mapping items must start at the same column at line 9, column 1: description: "GEO搜索占位架构师——AI搜索时代品牌霸屏利器,5维GEO评分+JSON-LD注入+评分门控,提升AI搜索引擎引用率。核心能力:… / FAQ Schema自动生成 / 5维GEO评分模型 / llms。Use when 需要AI模型调用、智能对话、Agent编排、LLM应用时使用。不… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - note
frontmatter-keyunknown frontmatter key "slug" - note
frontmatter-keyunknown frontmatter key "displayName" - note
frontmatter-keyunknown frontmatter key "summary" - note
frontmatter-keyunknown frontmatter key "homepage" - note
frontmatter-keyunknown frontmatter key "tools" - note
frontmatter-keyunknown frontmatter key "suggested_price" - note
frontmatter-keyunknown frontmatter key "pricing_tier" - note
frontmatter-keyunknown frontmatter key "pricing_model"
Process rating: all ten parameters 53/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
- 100Tools and files. Tools declared in frontmatter
- 100Steps. 69 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2304 tokens
- 100Running it twice. No mutating operations
- low 19 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
- +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
- +2Single-language instructions
- +3Description length 185: enough signal without eating the budget
- +4Structure: 44 headings
- +3Step-by-step instructions: 69 items
- +4Has examples (6 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.