AC daily-report
Generate a daily work report by automatically discovering all git repositories the user worked on, collecting commit logs across all branches, and summarizing CodeBuddy Agent session overviews. Supports any date via --date, --yesterday, or --days-ago flags. Use this skill when the user asks to generate a daily report, work summary, daily log, 日报, 工作日报, 今日工作总结, 昨日工作总结, or any variation of "what did I do today/yesterday".
Generate a daily work report by automatically discovering all git repositories the user worked on, collecting commit logs across all branches, and summarizing…
As a process C 52/100 · Has gaps — weak spots: result and completion, inputs and preconditions, consistency
The same skill appears in 1 more place: ClawHub
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: 6. 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 52/100
- 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
- 30Running it twice. 5 mutating operations with no state check
- 40Consistency. Frontmatter name (daily-report) differs from the folder (codebuddy-daily-report)
- 60Tools and files. Uses tools (python) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 70Failures and branches. 8 branches
- 100Steps. 16 steps
- 100Execution cost. Instruction body is 934 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
- +1No license
- +2Single-language instructions
- +3Description length 423: enough signal without eating the budget
- +4Structure: 9 headings
- +3Step-by-step instructions: 16 items
- +4Has examples (3 code blocks)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 87.