BC fee-collection
费用催缴管理技能。基于《C+基础保障服务手册-企服管理工作规程》第十一章，实现规范的费用催缴流程，包括智能分级催缴、个性化话术、能耗欠费合并计算等。触发场景：(1) 定时检查费用收缴状态（每天10:00），(2) 手动触发催缴检查（@企服助手 催缴检查），(3) 企微群关键词触发（@催缴），(4) 逾期分级处理（1-7天静默、8-30天推送、31天+ @all）。
费用催缴管理技能。基于《C+基础保障服务手册-企服管理工作规程》第十一章，实现规范的费用催缴流程，包括智能分级催缴、个性化话术、能耗欠费合并计算等。触发场景：(1) 定时检查费用收缴状态（每天10:00），(2) 手动触发催缴检查（@企服助手 催缴检查），(3) 企微群关键词触发（@催缴），(4)…
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 · 1
✓ No critical or high findings
Medium and low: 1
-
low Secrets in code
secret-high-entropy-tokenconfig/wecom_config.json:3High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"default_chat_id": "wrkS…8nQ",
quoted
Files scanned: 12. 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 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. 88 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 876 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
- -4Absolute local paths (C:\Users, /home/…): not portable
- -41 reference files, but SKILL.md never points to them: the model will not open them
- -35 of 5 scripts are never mentioned in SKILL.md
- +2Single-language instructions
- +3Description length 183: enough signal without eating the budget
- +4Structure: 40 headings
- +3Step-by-step instructions: 88 items
- +4Has examples (3 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 62.