AF report-generator
Automated sales and performance report generator for retail store managers. Generates daily, weekly, and monthly reports from POS/ERP data. Highlights anomalies, tracks targets, and delivers reports via configured channels. Use when a store manager asks for: 今天的销售, 日报, 周报, 月报, 销售额, 业绩怎么样, 完成率, 数据怎么样, daily report, sales summary, performance report, how did we do today, weekly summary, monthly review. Also triggers for scheduled automatic report delivery.
As a process F 33/100 · Will not run — References files that are not bundled: references/data-connectors.md
How to improve
- 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: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: references/data-connectors.md
Process rating: all ten parameters 33/100
- 0Tools and files. 1 referenced file(s) missing: references/data-connectors.md
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 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 (report-generator) differs from the folder (frank-report-generator)
- 55Failures and branches. 1 branches
- 100Steps. 21 steps
- 100Execution cost. Instruction body is 721 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
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 458: enough signal without eating the budget
- +4Structure: 12 headings
- +3Step-by-step instructions: 21 items
- +4Reference files are cited in the instructions (1 of 1)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 78.