BD deal-closer
产学研合作推进与落地决策引擎。当用户提交会议纪要、合作进展、对接记录，要求分析下一步、推进合作、判断成单概率、写跟进话术时触发。核心不是提醒，而是决策：基于会议内容推断对方真实需求、判断合作阶段与概率、给出最优策略动作和可直接使用的跟进话术。适用于钉钉听记/飞书妙记等会议纪要的结构化分析。配合 industry-signal-monitor（发现线索）和 industry-research（深度调研）形成完整链路。
As a process D 49/100 · Unfinished process — 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.
For the model run — optional
- 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: 4. 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")
Process rating: all ten parameters 49/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
- 40Consistency. Frontmatter name (deal-closer) differs from the folder (zhongguancun-deal-closer)
- 100Tools and files. No external tools needed
- 100Steps. 24 steps
- 100Execution cost. Instruction body is 480 tokens
- 100Running it twice. No mutating operations
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
- -5TODO / placeholder text left in the skill
- +1No license
- +2Single-language instructions
- +3Description length 209: enough signal without eating the budget
- +4Structure: 10 headings
- +3Step-by-step instructions: 24 items
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (2 of 2)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 71.
External checks
ClawHub: clean
This is a Markdown-only business meeting analysis skill that drafts partnership follow-ups and does not request system access, credentials, or automatic sending.
LLM: benign (high) · VirusTotal: · 29 May 2026