github-work-summary

Generates a categorized work summary from GitHub activity (PRs authored, issues created, code committed) for a given time period and organization, using parallel subagents for fast detail fetching. Use when the user asks "what did I work on", "what did I do last week", wants a work log, weekly update, standup notes, sprint recap, accomplishments list, performance review input, or any summary of their contributions. DO NOT TRIGGER for repository changelogs, release notes, or team-wide activity reports.

Quality

88%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

77%

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

This is a well-structured, actionable skill with clear step-by-step workflow, concrete commands, and useful guardrails (common mistakes table, inclusion/exclusion criteria). Its main weaknesses are minor verbosity in the opening sections and the lack of bundle files to support the referenced script path. The common mistakes table and output template are particularly strong additions that prevent real failure modes.

Suggestions

Trim or remove the 'Overview' and 'When to Use' sections since the process steps already make the purpose and usage clear, and this information is redundant with the skill description in frontmatter.

Include the referenced `collect_activity.py` script in the bundle or provide its expected input/output contract inline so the skill is self-contained.

Dimension	Reasoning	Score
Conciseness	The skill is mostly efficient but includes some unnecessary content like the 'When to Use' section which largely duplicates the skill description, and the 'Overview' section which restates what the process already makes clear. The tables and checklist add useful structure but some could be tightened.	2 / 3
Actionability	Provides concrete, executable commands (gh CLI calls, python script invocations), specific parameter tables, clear inclusion/exclusion criteria for contributions, and a complete output template with formatting guidelines. The guidance is specific and directly usable.	3 / 3
Workflow Clarity	The 5-step process is clearly sequenced with a progress checklist, explicit validation (checking gh auth status on failure), clear decision points (ask user if parameters are ambiguous), and a critical performance note about parallel subagent launching. The analyze step has a clear include/exclude table that prevents common errors.	3 / 3
Progressive Disclosure	The skill references a script at `skills/github-work-summary/scripts/collect_activity.py` but no bundle files are provided, making it impossible to verify the reference. The content is well-structured with sections but is somewhat long for a single file — the Common Mistakes table and Date Calculation Reference could potentially be separate references. However, the single-file organization is reasonable for this complexity level.	2 / 3
	Total	10 / 12 Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is an excellent skill description that excels across all dimensions. It provides specific concrete actions, comprehensive natural trigger terms that users would actually say, explicit 'Use when' and 'DO NOT TRIGGER' clauses, and clear boundaries that distinguish it from related skills like changelog generators or team activity reporters.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: 'Generates a categorized work summary from GitHub activity (PRs authored, issues created, code committed) for a given time period and organization, using parallel subagents for fast detail fetching.' This clearly describes what it does with specific data types and methods.	3 / 3
Completeness	Clearly answers both 'what' (generates categorized work summary from GitHub activity including PRs, issues, commits) and 'when' (explicit 'Use when...' clause with extensive trigger scenarios). Also includes a 'DO NOT TRIGGER' clause for negative cases, which adds further clarity.	3 / 3
Trigger Term Quality	Excellent coverage of natural trigger terms users would say: 'what did I work on', 'what did I do last week', 'work log', 'weekly update', 'standup notes', 'sprint recap', 'accomplishments list', 'performance review input', 'summary of their contributions'. These are highly natural phrases.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive with a clear niche: personal GitHub activity summaries. The explicit exclusion of 'repository changelogs, release notes, or team-wide activity reports' actively prevents conflicts with related but different skills. The specific mention of GitHub, personal contributions, and time periods creates a well-defined boundary.	3 / 3
	Total	12 / 12 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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: shousper/claude-kit
Commit: 08bc600

Reviewed: 14 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.