BF smarttable-weekly-check
企业微信智能表格周报检查工具。通过 Puppeteer 启动浏览器，利用内部 API 获取结构化数据，按4条规则检查组员周报质量。支持多周链接批量检查、自动登录等待、自动报告生成、项目维度汇总。触发词：智能表格周报检查、小组周报检查、周报链接检查、检查周报链接、smarttable check、数字员工周报检查。
企业微信智能表格周报检查工具。通过 Puppeteer 启动浏览器，利用内部 API 获取结构化数据，按4条规则检查组员周报质量。支持多周链接批量检查、自动登录等待、自动报告生成、项目维度汇总。触发词：智能表格周报检查、小组周报检查、周报链接检查、检查周报链接、smarttable check、数字员工周报检查。
As a process F 35/100 · Will not run — References files that are not bundled: scripts/extract_weekly.js
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: scripts/extract_weekly.js
Process rating: all ten parameters 35/100
- 0Tools and files. 1 referenced file(s) missing: scripts/extract_weekly.js
- 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
- 100Steps. 28 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1128 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
- +1No license
- +2Single-language instructions
- +3Description length 157: enough signal without eating the budget
- +4Structure: 21 headings
- +3Step-by-step instructions: 28 items
- +4Has examples (6 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 62.