BC project-site-selection-analysis
围绕项目落地需求与目标区域承载条件，综合评估项目与区域在土地空间、产业基础、政策支持、 交通物流、人才供给、配套服务、成本条件及风险约束等方面的匹配度，形成系统化的项目选址 分析报告。本技能核心解决"项目适不适合落在目标区域、为什么适合或不适合、落地优势和短板 是什么、需要哪些承接条件、是否具备招商落地可行性"等核心问题。本技能不是简单判断某个区域 "好不好"，而是围绕具体项目需求，分析区域是否具备承接该项目的现实条件、产业协同能力和 长期发展空间。当用户需要分析某项目是否适合落地某区域、评估项目选址可行性、对比多个区域 的项目承接能力、研究某产业项目落地条件、判断项目与园区/城市/区县的匹配度、为招商项目 提供落地研判、为企业投资扩产选择区域、分析项目落地风险和承接短板时，激活此技能。
围绕项目落地需求与目标区域承载条件，综合评估项目与区域在土地空间、产业基础、政策支持、 交通物流、人才供给、配套服务、成本条件及风险约束等方面的匹配度，形成系统化的项目选址 分析报告。本技能核心解决"项目适不适合落在目标区域、为什么适合或不适合、落地优势和短板…
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: 2. 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. 217 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1635 tokens
- 100Running it twice. No mutating operations
- low 16 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
- +4No input/output examples
- +2Single-language instructions
- +3Description length 348: enough signal without eating the budget
- +4Structure: 67 headings
- +3Step-by-step instructions: 217 items
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 66.