BD 评优激励通报分析
渠道/合作伙伴评优激励通报数据分析与欠缺诊断，并配套销售合作伙伴政策文档的分析与检索。当用户上传或引用「评优激励通报」「渠道评优」「合作伙伴评优激励」「激励核算」类 Excel（含县市汇总、渠道完成情况、否决门槛值等工作表），要求分析数据欠缺、找出需要加强改进的薄弱环节、生成 Word 分析报告或网格整改清单、渠道预警分级、名单导出、图表可视化时使用；当用户引用销售合作伙伴政策类 Word 文档（管理办法、运营执行要求、分级施策指导意见等）并要求总结政策规则、按政策文档检索回答问题时也使用。支持八种交互模式：模式0 说「帮我分析/有什么功能」先列菜单等选择；①询问具体内容/指标；②询问具体网格或渠道；③总结分析输出 Word；④生成预警分级名单 Excel；⑤生成可视化看板/图表；⑥政策文档分析（总结内容、说明政策规则）；⑦政策文档检索问答（定位条款、引用原文出处）。关键词：评优激励、渠道评优、合作伙伴评优、激励通报、数据欠缺分析、短板诊断、否决门槛、终端合约率、APP融合率、重点业务牵引系数、弱势网格、网格整改清单、网格汇总表、预警分级、红黄牌、重点整改名单、可视化看板、图表、政策文档、管理办法、运营执行要求、分级施策、政策检索、政策问答、政策速查手册、帮我分析、有什么功能、某指标情况、某网格怎么样、某渠道怎么样。
渠道/合作伙伴评优激励通报数据分析与欠缺诊断，并配套销售合作伙伴政策文档的分析与检索。当用户上传或引用「评优激励通报」「渠道评优」「合作伙伴评优激励」「激励核算」类 Excel（含县市汇总、渠道完成情况、否决门槛值等工作表），要求分析数据欠缺、找出需要加强改进的薄弱环节、生成 Word…
As a process D 41/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.
- 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: 11. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - note
frontmatter-keyunknown frontmatter key "agent_created"
Process rating: all ten parameters 41/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 (评优激励通报分析) differs from the folder (report-analysis)
- 60Tools and files. Uses tools (python) that frontmatter does not declare
- 100Steps. 111 steps
- 100Execution cost. Instruction body is 2765 tokens
- 100Running it twice. No mutating operations
- low 13 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
- +1No license
- +2Single-language instructions
- +3Description length 567: enough signal without eating the budget
- +4Structure: 29 headings
- +3Step-by-step instructions: 111 items
- +4Has examples (1 code blocks)
- +3All 8 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 69.