BC investment-project-assessment
围绕目标企业或招商项目的产业属性、投资规模、落地条件、产业带动能力、经济贡献潜力、 区域匹配度、投资可行性及风险约束等核心维度,系统评估该企业或项目是否值得招引、是否适合落地、 落地后能为区域带来什么价值,以及推进过程中需要重点关注哪些风险。本技能核心解决"这个项目值不值得招、 能不能落、落地价值有多大、对产业有没有带动、投资是否可行、政府应如何推进"等核心问题。 当用户需要评估招商项目、筛选招商线索、判断项目投资价值、分析项目产业带动能力、 为招商项目上会决策提供材料、对比多个招商项目优先级、判断项目落地条件成熟度、 形成招商项目评估报告时,激活此技能。
围绕目标企业或招商项目的产业属性、投资规模、落地条件、产业带动能力、经济贡献潜力、 区域匹配度、投资可行性及风险约束等核心维度,系统评估该企业或项目是否值得招引、是否适合落地、 落地后能为区域带来什么价值,以及推进过程中需要重点关注哪些风险。本技能核心解决"这个项目值不值得招、…
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. 229 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1471 tokens
- 100Running it twice. No mutating operations
- low 15 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 281: enough signal without eating the budget
- +4Structure: 56 headings
- +3Step-by-step instructions: 229 items
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 66.