CtrlK
BlogDocsLog inGet started
Tessl Logo

pr-description

Update a GitHub PR description with a summary of changes

79

2.17x
Quality

Does it follow best practices?

Impact

100%

2.17x

Average score across 3 eval scenarios

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

85%

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

The body delivers concrete, executable guidance with a well-sequenced workflow and verification checklist. Its main weakness is mild redundancy between the section templates and the 'Example Output' illustration.

Suggestions

Trim the 'Example Output' section or fold it into one of the format examples to remove duplicated content.

Consider a brief explicit verification step (e.g. 'Preview the rendered description before posting') to reinforce the checklist.

DimensionReasoningScore

Conciseness

Mostly efficient with concrete commands and no extraneous concept explanations, but the 'Example Output' section repeats the format templates already shown, so it could be tightened.

2 / 3

Actionability

Provides executable commands (`git log main..HEAD --oneline`, `git diff main..HEAD`), concrete argument syntax, and copy-paste-ready markdown templates for every section.

3 / 3

Workflow Clarity

A clearly numbered 4-step sequence with a decision checkpoint in step 2 (skip if already complete) and a closing checklist that serves as explicit verification.

3 / 3

Progressive Disclosure

A single-purpose skill with no bundle files, organized into well-labeled sections (Arguments, Instructions, Format, Guidelines, Checklist) that keep the overview self-contained.

3 / 3

Total

11

/

12

Passed

Description

50%

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 clear and concise about what the skill does but omits any explicit usage trigger, leaving the 'when' question unanswered. It is reasonably specific to the PR-description niche yet could be more distinctive with concrete trigger terms.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when the user asks to update or generate a pull request description from recent changes.'

Expand the action list beyond 'update' to cover 'generate', 'refresh', or 'summarize' PR descriptions.

Include common trigger terms like 'pull request', 'release notes', and 'PR summary' for better recall.

DimensionReasoningScore

Specificity

Names the domain (GitHub PR description) and a single action ('Update ... with a summary of changes'), but does not list multiple concrete actions, falling short of comprehensive.

2 / 3

Completeness

States what the skill does but lacks any 'Use when...' trigger guidance, which per the rubric caps completeness at 2.

2 / 3

Trigger Term Quality

Includes relevant natural terms ('GitHub PR description', 'PR', 'changes') but misses common variations like 'pull request' or 'release notes'.

2 / 3

Distinctiveness Conflict Risk

Targets a fairly specific niche (PR descriptions) but without explicit triggers could still overlap with general git/PR skills.

2 / 3

Total

8

/

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
pipecat-ai/pipecat
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.