what-did-i-get-done

Summarize authored commits over a user-specified time period into a concise update

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./cursor-team-kit/skills/what-did-i-get-done/SKILL.md

Quality

Content

92%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A tightly written, well-structured simple skill: concise, clearly sequenced, and well-organized with no unnecessary references. The only gap is the absence of concrete git commands, which keeps actionability just short of perfect.

Suggestions

Optionally include a concrete example command such as `git log --author=<email> --since=<date> --until=<date> --no-merges` to make the workflow copy-paste executable and lift actionability to 5.

Dimension	Reasoning	Score
Conciseness	The body is lean and information-dense with no padding or explanation of concepts Claude already knows; every section (Trigger, Workflow, Guardrails, Output) earns its place.	5 / 5
Actionability	Steps give concrete, executable filtering criteria ('commits authored by the current git user email', 'Exclude merge commits and uncommitted changes'), but no specific git commands are provided, leaving a minor gap; guidance is actionable for an instruction-only skill.	4 / 5
Workflow Clarity	A clear, unambiguous five-step sequence for a simple read-only summarization task; no destructive/batch validation cap applies, and the simple-skill exception supports a top score for a well-sequenced single-purpose workflow.	5 / 5
Progressive Disclosure	Under 50 lines with no need for external references; content is organized into clearly labeled sections (Trigger, Workflow, Guardrails, Output), satisfying the simple-skill progressive-disclosure criterion.	5 / 5
	Total	19 / 20 Passed

Description

53%Weight 40%Scale 1-5

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 is clear and specific about the what (summarizing authored commits in a time window) but omits any explicit when-to-use trigger guidance, which caps completeness and limits trigger term coverage.

Suggestions

Add an explicit 'Use when...' clause with natural trigger phrases, e.g. 'Use when the user asks what they got done, wants a standup summary, or needs a recap of recent commits.'

Include natural synonyms users actually say (e.g. 'what did I get done', 'standup', 'git log') to improve trigger term coverage.

Optionally enumerate 1-2 more concrete actions (e.g. 'read commits, filter merges, synthesize bullets') to lift specificity toward 4-5.

Dimension	Reasoning	Score
Specificity	Names the domain (authored commits over a time period) and one concrete action ('Summarize... into a concise update'), but stops at a single action rather than enumerating several, matching the anchor for 1-2 concrete actions.	3 / 5
Completeness	Clearly states what the skill does, but there is no 'Use when...' or equivalent trigger guidance; per the rubric, a missing explicit 'when' clause caps completeness at 3.	3 / 5
Trigger Term Quality	Includes some relevant keywords ('commits', 'time period', 'update') but lacks common natural variations users would say ('what did I get done', 'standup', 'git log') and any explicit trigger phrasing.	3 / 5
Distinctiveness Conflict Risk	The commit-summary-over-a-time-range niche is fairly distinct with only minor overlap risk against general git/commit skills; not a 5 because no explicit trigger phrases sharpen the niche.	4 / 5
	Total	13 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: cursor/plugins
Path: cursor-team-kit/skills/what-did-i-get-done/SKILL.md
Commit: 51a96e0

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.