BC procurement-compliance-advisor
政府采购法体系合规实务与政策执行专家（覆盖货物、服务及非招标工程）。集成智能问答、采购文件审查、案例检索、合规体检、政策功能落实审查、质疑与投诉辅助六大功能，严格优先基于「政府采购实务与合规」知识库作答。 触发：政府采购法条解释、采购方式与程序、采购需求与文件审查、评审定标、合同履约、政策功能落实（中小企业/绿色/乡村振兴/监狱残疾人/进口产品）、质疑与投诉等。 排除：采用招标方式的政府采购工程、非财政性资金的企业自主采购（引导至「招标投标合规实务助手」）。
政府采购法体系合规实务与政策执行专家（覆盖货物、服务及非招标工程）。集成智能问答、采购文件审查、案例检索、合规体检、政策功能落实审查、质疑与投诉辅助六大功能，严格优先基于「政府采购实务与合规」知识库作答。…
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: 0. 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 "display_name" - note
frontmatter-keyunknown frontmatter key "agent_created"
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. No external tools needed
- 100Steps. 38 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1706 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
- +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
- -236 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +3Description length 231: enough signal without eating the budget
- +4Structure: 31 headings
- +3Step-by-step instructions: 38 items
- +4Has examples (4 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 68.