summarize-github-issue-pr-notification

Summarizes the content of a GitHub issue, pull request (PR), or notification, providing a concise overview of the main points and key details. ALWAYS use the skill when asked to summarize an issue, PR, or notification.

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./src/lm/skills/summarize-github-issue-pr-notification/SKILL.md

Quality

Content

71%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 compact, well-structured instruction skill with concrete templates and a built-in length-check verification. The main drag is conciseness: the Purpose/Usage prose duplicates the frontmatter description and adds mild over-explanation.

Suggestions

Collapse the Purpose and Usage prose into the description or trim it to one line, since both restate what the frontmatter already says; this is the lowest-scoring dimension.

Drop the justification "Images are important visual content and should not be removed or summarized" and keep just the directive "preserve image Markdown exactly as it appears".

Convert the Tips list into a short ordered checklist ending with the length-check to make the implicit validate step an explicit workflow checkpoint.

Dimension	Reasoning	Score
Conciseness	Mostly efficient, but the Purpose and Usage sections restate the description, and phrases like "This skill helps users quickly understand the essence of an issue without having to read through the entire content" and "Images are important visual content and should not be removed or summarized" add explanation Claude does not need.	3 / 5
Actionability	Provides concrete, copy-paste-ready templates (Markdown link patterns for issues/pulls, the @author: comment format) plus specific rules (preserve images verbatim, keep summary shorter than source), with only minor gaps such as no example of a finished summary.	4 / 5
Workflow Clarity	As a simple single-action skill the task is unambiguous, and the final bullet ("Make sure the summary is at least as short or shorter than...") acts as a verification checkpoint; it falls just short of 5 because the tips are an unordered list rather than an explicit validate/fix loop.	4 / 5
Progressive Disclosure	Under 50 lines with no need for external references and no bundle files present; the body is organized into clear Purpose, Usage, and Tips sections, satisfying the simple-skill exception for a 5.	5 / 5
	Total	16 / 20 Passed

Description

82%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.

A strong description: third-person voice, explicit what-and-when trigger clause, and a well-scoped niche. Its main limitation is specificity, since it describes essentially one action (summarize) without enumerating variant capabilities.

Suggestions

Add one or two more concrete actions to lift specificity (e.g. "highlights key decisions, open questions, and referenced issues/PRs") so coverage reads as comprehensive rather than a single action.

Include a couple of natural synonyms in the trigger clause (e.g. "discussion", "thread", "comment thread") to push trigger-term coverage toward 5.

Dimension	Reasoning	Score
Specificity	Names the domain ("GitHub issue, pull request (PR), or notification") and one concrete action ("Summarizes the content... providing a concise overview of the main points and key details"), but offers only a single action rather than comprehensive coverage, matching the anchor for 1-2 concrete actions.	3 / 5
Completeness	It explicitly answers both what ("Summarizes the content... providing a concise overview of the main points and key details") and when ("ALWAYS use the skill when asked to summarize an issue, PR, or notification") with concrete trigger phrases, matching the 5 anchor.	5 / 5
Trigger Term Quality	Natural user-facing keywords are present ("summarize", "issue", "PR", "notification") in the trigger clause "when asked to summarize an issue, PR, or notification", giving good coverage; a few synonyms or phrasings (e.g. "thread", "discussion") are missing, so it stops short of 5.	4 / 5
Distinctiveness Conflict Risk	The niche is clearly scoped to summarizing GitHub issues/PRs/notifications with distinct triggers, presenting minimal overlap risk with other skills.	5 / 5
	Total	17 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 1 missing	Warning

	Total	15 / 16 Passed

Repository: microsoft/vscode-pull-request-github
Path: src/lm/skills/summarize-github-issue-pr-notification/SKILL.md
Commit: 849821a

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