BF weigui-weekly-report
生成、筛选或解读上市公司违规案例周报,只使用聚源违规案例库及其关联表,并按 LatestInfoPublDate(公告日期/发布时间)选取连续 7 个自然日。用户要求“违规案例周报”“最近一周违规处罚案例”“本周处罚对象、违规事项、处罚情况或法规依据汇总”,或要求输出可交付 Word、JSON、Markdown 时使用。
生成、筛选或解读上市公司违规案例周报,只使用聚源违规案例库及其关联表,并按 LatestInfoPublDate(公告日期/发布时间)选取连续 7 个自然日。用户要求“违规案例周报”“最近一周违规处罚案例”“本周处罚对象、违规事项、处罚情况或法规依据汇总”,或要求输出可交付 Word、JSON、Markdown…
As a process F 28/100 · Will not run — References files that are not bundled: references/schema.md, scripts/build-weekly-word.py
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The text references files that are not there: add them or drop the references.
- 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") - warning
missing-refreference to a missing file: references/schema.md - warning
missing-refreference to a missing file: scripts/build-weekly-word.py
Process rating: all ten parameters 28/100
- 0Tools and files. 2 referenced file(s) missing: references/schema.md, scripts/build-weekly-word.py
- 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. 1 mutating operations with no state check
- 40Consistency. Frontmatter name (weigui-weekly-report) differs from the folder (weekly-report-companies-violations)
- 100Steps. 42 steps
- 100Execution cost. Instruction body is 811 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
- +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
- +5Description quotes 3 example trigger phrases
- +3Description length 161: enough signal without eating the budget
- +4Structure: 6 headings
- +3Step-by-step instructions: 42 items
- +4Has examples (4 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 68.