BD SRM-Yidea-Procurement
SRM供应商关系管理系统完整解决方案 - 业务+技术一体化。覆盖供应商档案、采购申请、询价申请、询价结果确认、合同起草、采购订单、价格库管理、配额管理、收货管理、付款计划、供应商扣款、付款申请、物料档案等功能,同时集成鲸采云表单SDK技术底座,支持表单提交、查询、修改、用户确认机制。Keywords: SRM, 供应商管理, 采购管理, 询比价, 合同管理, 鲸采云, 表单处理, MCP.
SRM供应商关系管理系统完整解决方案 - 业务+技术一体化。覆盖供应商档案、采购申请、询价申请、询价结果确认、合同起草、采购订单、价格库管理、配额管理、收货管理、付款计划、供应商扣款、付款申请、物料档案等功能,同时集成鲸采云表单SDK技术底座,支持表单提交、查询、修改、用户确认机制。Keywords: SRM…
As a process D 39/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: 14. 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")
Process rating: all ten parameters 39/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
- 30Running it twice. 2 mutating operations with no state check
- 40Consistency. Frontmatter name (SRM-Yidea-Procurement) differs from the folder (srm)
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 100Steps. 12 steps
- 100Execution cost. Instruction body is 1730 tokens
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
- -218 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +3Description length 196: enough signal without eating the budget
- +4Structure: 14 headings
- +3Step-by-step instructions: 12 items
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (6 of 6)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 69.