AB weekly-report-generator
Generate polished Chinese R&D weekly reports from recent work logs, chat history, commit notes, or development notes. Use when the user asks to 生成、整理、润色、汇总本周、上周、最近7天或某日期范围的周报/研发周报, especially for tender-agent, RAG, prompt, skill, document parsing, table parsing, scoring-standard, content-generation, export-center, and Agent work. Automatically filters deployment, environment, operations, installation, and troubleshooting details.
Generate polished Chinese R&D weekly reports from recent work logs, chat history, commit notes, or development notes.
As a process B 68/100 · Nearly there — weak spots: failures and branches, consistency, running it twice
How to improve
- 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: 5. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 68/100
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 5 mutating operations with no state check
- 40Consistency. Frontmatter name (weekly-report-generator) differs from the folder (weekly-report-skill)
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Tools and files. No external tools needed
- 100Steps. 46 steps
- 100Execution cost. Instruction body is 936 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)
- +1No license
- +2Single-language instructions
- +3Description length 433: enough signal without eating the budget
- +4Structure: 8 headings
- +3Step-by-step instructions: 46 items
- +3Output format is stated explicitly
- +4Has examples (3 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 87.