AC investment-attraction-action-guide
围绕目标产业发展趋势、产业链结构特征、区域承载禀赋、精准招商方向、分层目标企业、多元招商路径、 企业触达策略、项目落地条件、全周期行动计划核心维度，依托公开合规产业与招商数据，搭建覆盖 “产业研判—区域定位—招商方向—目标企业—触达路径—项目策划—落地保障—行动计划”的标准化 实操型招商行动指南生成体系。本技能核心解决“特定产业招商招什么、去哪招、招谁、怎么招、 如何高效触达、如何落地保障、分阶段如何推进”全链条实战问题，彻底打通产业研究到招商落地的闭环链路。 当用户需要定制细分产业招商行动指南、生成标准化产业招商落地方案、研判特定区域产业招商打法、 梳理细分赛道精准招商方向、搭建产业链补链强链招商路径、分层筛选招商目标企业资源或设计全周期 招商行动计划时，激活此技能。
围绕目标产业发展趋势、产业链结构特征、区域承载禀赋、精准招商方向、分层目标企业、多元招商路径、 企业触达策略、项目落地条件、全周期行动计划核心维度，依托公开合规产业与招商数据，搭建覆盖 “产业研判—区域定位—招商方向—目标企业—触达路径—项目策划—落地保障—行动计划”的标准化…
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. 165 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2146 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 339: enough signal without eating the budget
- +4Structure: 49 headings
- +3Step-by-step instructions: 165 items
- +4Has examples (1 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.