what-did-i-get-done
Summarize authored commits over a user-specified time period into a concise update
70
62%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./cursor-team-kit/skills/what-did-i-get-done/SKILL.mdQuality
Discovery
40%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description identifies a clear and distinct capability—summarizing authored commits over a time period—but lacks explicit trigger guidance ('Use when...') and misses common natural language terms users might employ. It is concise and specific enough to avoid conflicts but would benefit from richer trigger terms and an explicit 'when to use' clause.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks for a summary of recent work, standup notes, or a changelog based on git commits.'
Include natural trigger term variations such as 'git log', 'standup update', 'what did I do', 'weekly summary', 'changelog', and 'commit history'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (authored commits) and a specific action (summarize into a concise update), but only describes one action rather than listing multiple concrete capabilities. | 2 / 3 |
Completeness | Describes what the skill does (summarize commits over a time period) but has no explicit 'Use when...' clause or trigger guidance, which per the rubric caps completeness at 2, and the 'when' is entirely missing, warranting a 1. | 1 / 3 |
Trigger Term Quality | Includes relevant terms like 'commits', 'summarize', and 'time period', but misses common user variations such as 'git log', 'what did I work on', 'standup', 'status update', 'changelog', or 'weekly summary'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of 'authored commits', 'time period', and 'summarize' creates a clear niche that is unlikely to conflict with other skills—it's distinctly about commit summarization over a date range. | 3 / 3 |
Total | 8 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A well-structured, concise skill that clearly defines its purpose, workflow, and output format. Its main weakness is the lack of concrete git commands—providing the actual `git log` invocation with appropriate flags would make it fully actionable rather than relying on Claude to figure out the right command and format options.
Suggestions
Add the concrete git command to use, e.g., `git log --author="$(git config user.email)" --after="2024-01-01" --no-merges --format="%h %s" | head -50` so the skill is copy-paste executable.
Include a brief example of expected output format (e.g., a sample status update with date range and bullets) to remove ambiguity about the final deliverable.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every line serves a purpose. No unnecessary explanations of git concepts, no padding. The skill assumes Claude knows how to run git commands and synthesize information. | 3 / 3 |
Actionability | The workflow describes what to do at a conceptual level but lacks concrete git commands (e.g., `git log --author=... --after=... --no-merges --format=...`). It's clear direction but not copy-paste executable. | 2 / 3 |
Workflow Clarity | For this relatively simple, non-destructive read-only task, the 5-step sequence is clear and logically ordered. No destructive or batch operations are involved, so validation checkpoints are not required. The workflow is unambiguous. | 3 / 3 |
Progressive Disclosure | This is a simple, single-purpose skill under 50 lines with no need for external references. The content is well-organized into clear sections (Trigger, Workflow, Guardrails, Output) that are easy to scan. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- cursor/plugins
- Commit
7dd9fea
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.