AB git-standup
Generate concise daily/weekly standup summaries from git commit history. Analyzes recent commits, groups them by type (features, fixes, refactors, chores), and produces a standup-ready status report. Use when the user wants to: (1) Generate a daily standup summary for yourself or your team, (2) See what everyone worked on yesterday, (3) Prepare for daily scrum meetings, (4) Get a weekly activity digest, (5) Track progress on a specific branch or feature, (6) Generate a status report for your manager. Best for developers, engineering teams, remote workers, scrum masters, and anyone who needs quick git-based status reports.
As a process B 66/100 · Nearly there — weak spots: inputs and preconditions, failures and branches, consistency
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: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 66/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 30Running it twice. 11 mutating operations with no state check
- 40Consistency. Frontmatter name (git-standup) differs from the folder (git-standup-summary)
- 60Result and completion. Output format stated, no completion criterion
- 100Tools and files. No external tools needed
- 100Steps. 25 steps
- 100When it triggers. States when to use and when not to
- 100Execution cost. Instruction body is 857 tokens
- 100Progress reporting. Reports progress
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
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 629: enough signal without eating the budget
- +4Structure: 15 headings
- +3Step-by-step instructions: 25 items
- +3Output format is stated explicitly
- +4Has examples (8 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 90.