CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

70

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

72%

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

The body is highly actionable and well organized with a verified script reference, but it carries minor redundancy and lacks an explicit validation/feedback loop for its batch fetch operation, capping conciseness and workflow clarity at 2.

Suggestions

Add a validation/retry step after the parallel subagent fetch (e.g., check that every PR/issue returned detail JSON; re-fetch any that failed) so the batch operation has a feedback loop.

Remove the standalone "Data Collection Script" section that restates the path from Step 2, and trim the "When to Use" bullets that duplicate the frontmatter description.

DimensionReasoningScore

Conciseness

Mostly efficient with no concept-padding, but the "Data Collection Script" section restates the path already given in Step 2 and "When to Use" repeats the frontmatter, so it could be tightened.

2 / 3

Actionability

Fully executable, copy-paste-ready commands (python3 .../collect_activity.py, gh pr view --json ...) plus a concrete output template and analysis table.

3 / 3

Workflow Clarity

A clear 5-step sequence with a progress checklist and a script-failure checkpoint is present, but the batch parallel-fetch operation lacks a validate/fix/retry feedback loop, which caps this dimension at 2.

2 / 3

Progressive Disclosure

The single bundle file collect_activity.py is referenced at the stated path and exists; the body is organized into clear sections with one-level references appropriate for a single-purpose skill.

3 / 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.

The description is strong across all dimensions: concrete actions, excellent natural trigger terms, complete what/when guidance, and a distinctive niche with an explicit exclusion clause. It is a model description with no meaningful weaknesses.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ("Generates a categorized work summary", "PRs authored, issues created, code committed", "parallel subagents"), matching the top anchor.

3 / 3

Completeness

Explicitly answers both what ("Generates a categorized work summary from GitHub activity") and when ("Use when the user asks...") with explicit triggers.

3 / 3

Trigger Term Quality

Strong coverage of natural phrases users say ("what did I work on", "what did I do last week", "standup notes", "sprint recap", "accomplishments list", "performance review input").

3 / 3

Distinctiveness Conflict Risk

Clear personal-GitHub-work niche with an explicit "DO NOT TRIGGER" boundary against changelogs, release notes, and team-wide reports, making misfiring unlikely.

3 / 3

Total

12

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
shousper/claude-kit
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.