AC enterprise-contact-path-mining
围绕目标企业的组织结构、关键部门、管理团队、对外投资、上下游合作、公开联系方式、合作机构、 产业园区、行业协会、投融资关系、招投标关系及公开活动轨迹等信息,系统挖掘企业可触达路径, 形成覆盖“企业入口—关键角色—关联机构—合作网络—产业链关系—投资线索—沟通切入点—触达策略” 的企业触达分析体系。本技能核心解决“对接企业时从哪里切入、找谁切入、通过什么渠道切入、 用什么理由切入、如何提升触达成功率”的关键问题。当用户需要挖掘企业触达路径、查询企业对接渠道、 梳理联系人线索、设计企业拜访策略、寻找招商合作切入点、分析企业关联机构、查询企业投资扩产线索 或开展招商对接前期筹备时,激活此技能。
围绕目标企业的组织结构、关键部门、管理团队、对外投资、上下游合作、公开联系方式、合作机构、 产业园区、行业协会、投融资关系、招投标关系及公开活动轨迹等信息,系统挖掘企业可触达路径, 形成覆盖“企业入口—关键角色—关联机构—合作网络—产业链关系—投资线索—沟通切入点—触达策略”…
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: 3. 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. 135 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1763 tokens
- 100Running it twice. No mutating operations
- low 11 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 297: enough signal without eating the budget
- +4Structure: 40 headings
- +3Step-by-step instructions: 135 items
- +4Has examples (1 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.