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

67%

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-only skill with concrete formatting rules and a clear single action. Its main weakness is conciseness, since the Purpose and Usage sections repeat the description and each other rather than adding new guidance.

Suggestions

Collapse the redundant 'Purpose' and 'Usage' sections into a single concise statement; the description already conveys what the skill does, so the body should focus only on how to format output.

Add one complete worked example showing a full summarized output (title, key points, comment list) so the formatting rules can be applied as a copy-paste-ready template.

State the input expectation explicitly as a short step ('Parse the provided JSON issue/PR/notification, then emit the summary using these rules') to turn the tips list into a clear two-step sequence.

Dimension	Reasoning	Score
Conciseness	The 'Purpose' and 'Usage' sections restate the description nearly verbatim ('summarizes the content, providing a concise overview of the main points and key details') and explain the obvious value of summarization, so the body is mostly efficient but padded with redundant explanation; not a 4 because the redundancy is noticeable.	3 / 5
Actionability	Provides concrete directives (no code output, Markdown links for references, author-first comment format with an example, preserve images verbatim, summary shorter than source) that are mostly executable; the minor gap is the absence of a full worked output example showing the complete summary structure.	4 / 5
Workflow Clarity	As a simple single-purpose skill the action is unambiguous (JSON input to summary output) with clear formatting tips, but the body presents rules rather than an explicit extract-then-summarize sequence, so it sits just below the 5 anchor for simple skills.	4 / 5
Progressive Disclosure	The skill is under 50 lines with no bundle files present and no need for external references; content is organized into three clear sections (Purpose, Usage, Tips), which meets the simple-skill exception for a 5.	5 / 5
	Total	16 / 20 Passed

Description

63%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, third-person description that explicitly covers both what the skill does and when to use it with concrete trigger phrases. Its main weakness is specificity, since it restates a single summarization action rather than enumerating several distinct capabilities.

Dimension	Reasoning	Score
Specificity	Names the domain ('GitHub issue, pull request (PR), or notification') and the action 'Summarizes the content' but essentially restates one action ('providing a concise overview of the main points and key details') rather than listing several distinct capabilities, so it is not comprehensive enough for a 4.	3 / 5
Completeness	Clearly states what it does ('Summarizes the content... providing a concise overview') and explicitly states when to use it ('ALWAYS use the skill when asked to summarize an issue, PR, or notification'), matching the anchor for explicit what-and-when with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural user terms ('summarize an issue, PR, or notification', 'GitHub issue', 'pull request (PR)', 'notification') with good coverage of the abbreviation; a few synonyms (e.g. 'thread', 'discussion') are missing, keeping it just below 5.	4 / 5
Distinctiveness Conflict Risk	The GitHub-issue/PR/notification niche has distinct triggers and minimal conflict risk, but 'summarize' is a broad verb that could overlap slightly with general summarization skills, so it is mostly distinct rather than a clear 5.	4 / 5
	Total	16 / 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: 2f06150

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