pr-description
Update a GitHub PR description with a summary of changes
68
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
32%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 identifies a specific GitHub-related task but is too brief and lacks explicit trigger guidance. It fails to include a 'Use when...' clause, which is critical for skill selection, and doesn't enumerate the full scope of capabilities or natural user phrases that would invoke this skill.
Suggestions
Add a 'Use when...' clause with trigger terms like 'pull request description', 'PR summary', 'update PR', 'summarize changes for PR'
Expand the capability description to include specific actions like 'analyzes commits, generates summary, updates PR body via GitHub API'
Include common variations of terminology: 'pull request', 'PR', 'merge request description'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (GitHub PR) and one action (update description with summary), but doesn't list multiple concrete actions or detail what 'summary of changes' entails. | 2 / 3 |
Completeness | Describes what it does but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes 'GitHub PR description' and 'summary of changes' which are relevant, but misses common variations like 'pull request', 'PR summary', 'update PR', or 'describe changes'. | 2 / 3 |
Distinctiveness Conflict Risk | Specific to GitHub PRs which provides some distinction, but could overlap with general GitHub skills or commit message skills without clearer boundaries. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
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 workflow steps and concrete examples. The main weakness is some redundancy between sections (format examples, example output, and checklist overlap) that could be tightened. The skill effectively guides Claude through the PR description update process with appropriate validation checkpoints.
Suggestions
Remove the checklist section as it largely restates the guidelines and step 2 validation already covered
Consolidate the 'PR Description Format' section and 'Example Output' section to avoid duplication - one complete example is sufficient
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some redundancy - the example output section largely duplicates the format section, and the checklist at the end restates guidelines already covered. Some sections could be tightened. | 2 / 3 |
Actionability | Provides concrete, executable commands (git log, git diff), specific markdown formats with copy-paste ready examples, and clear argument syntax. The instructions are specific and actionable throughout. | 3 / 3 |
Workflow Clarity | Clear 4-step sequence with explicit validation checkpoint (step 2 checks if update is needed before proceeding). The workflow includes decision points and the checklist provides verification before the final action. | 3 / 3 |
Progressive Disclosure | Content is reasonably structured with clear sections, but everything is inline in one file. For a skill of this length (~100 lines), some content like the detailed PR description format could be split out, though the current organization is functional. | 2 / 3 |
Total | 10 / 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- 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.