AC enterprise-investment-attraction-feasibility
围绕目标企业扩产动向、跨区域布局需求、迁址潜在诉求、产业赛道适配度、区域承载能力、 本地产业链协同、公开可验证政企链接、合规触达路径及项目落地风险等核心维度,依托公开合规信息, 搭建覆盖“企业招引价值—扩产迁址信号—产业匹配度—区域承载条件—本地关联网络—合规触达路径— 招引可行性定级—落地策略与风险防控”的全维度招商研判分析体系。本技能核心解决“目标企业是否 值得招引、是否具备扩产迁址需求、能否在本地落地、有无合规对接入口、如何精准推进招引工作” 等招商核心决策问题。当用户需要分析企业招引可行性、判断企业招引价值、研判企业扩产迁址需求、 评估企业区域落地适配性、核查本地产业协同关系、挖掘合规触达路径或制定专项招引策略时, 激活此技能。
围绕目标企业扩产动向、跨区域布局需求、迁址潜在诉求、产业赛道适配度、区域承载能力、 本地产业链协同、公开可验证政企链接、合规触达路径及项目落地风险等核心维度,依托公开合规信息, 搭建覆盖“企业招引价值—扩产迁址信号—产业匹配度—区域承载条件—本地关联网络—合规触达路径—…
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. 148 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2290 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 322: enough signal without eating the budget
- +4Structure: 49 headings
- +3Step-by-step instructions: 148 items
- +4Has examples (1 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.