AC investment-competition-regional-comparison
围绕多目标区域产业基础、政策支撑体系、营商环境能级、综合落地成本、全维度要素保障、 专业园区承载、企业集聚质量、项目落地转化效率、综合招商竞争力核心维度，依托公开合规数据， 搭建覆盖“区域基础禀赋—产业承载条件—政策环境能级—成本要素体系—营商服务能力—招商核心优势— 短板风险研判—差异化竞争策略”的标准化区域招商对比分析体系。本技能核心解决“多区域招商竞争 实力排序、各区域核心优势禀赋、招商短板与竞争壁垒、目标产业最优承接区域、本地招商竞争力差距、 差异化招商打法与突围路径”等招商研判、项目选址、区域对标、政策优化核心问题。当用户需要 多区域招商竞争力横向对比、区域招商优势差异研判、本地与竞品区域差距剖析、目标产业落地最优区域 筛选、园区承载条件对标分析或定制区域差异化招商策略时，激活此技能。
围绕多目标区域产业基础、政策支撑体系、营商环境能级、综合落地成本、全维度要素保障、 专业园区承载、企业集聚质量、项目落地转化效率、综合招商竞争力核心维度，依托公开合规数据， 搭建覆盖“区域基础禀赋—产业承载条件—政策环境能级—成本要素体系—营商服务能力—招商核心优势—…
As a process C 53/100 · Has gaps — 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: 0. 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 "slug" - note
frontmatter-keyunknown frontmatter key "displayName" - note
frontmatter-keyunknown frontmatter key "summary" - note
frontmatter-keyunknown frontmatter key "triggers" - note
frontmatter-keyunknown frontmatter key "parameters" - note
frontmatter-keyunknown frontmatter key "tools"
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. 151 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2084 tokens
- 100Running it twice. No mutating operations
- low 12 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)
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +5Description quotes 2 example trigger phrases
- +3Description length 352: enough signal without eating the budget
- +4Structure: 51 headings
- +3Step-by-step instructions: 151 items
- +4Has examples (1 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.