CtrlK
BlogDocsLog inGet started
Tessl Logo

gh-pr-description

Drafts and reviews GitHub pull request descriptions for the eve repository. Use when opening, updating, or reviewing a PR, or when summarizing a branch for reviewers.

69

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

86%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 tight, well-structured instruction skill that gives specific, actionable PR-writing guidance with a clear workflow and validation cues. Adding a short example of a finished PR body would round out actionability.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence: no preamble on what a PR or GitHub is, and every bullet gives actionable guidance rather than explanation, so every token earns its place.

5 / 5

Actionability

Concrete, executable guidance is present (fill '.github/pull_request_template.md', run 'gh pr create/edit ... --body-file', use 'Closes #N'), but a worked example of a completed description would push it to fully copy-paste-ready.

4 / 5

Workflow Clarity

A clear Inspect -> Write -> Publish sequence with checkpoints ('check only verified items', pre-publish 'confirm the Summary leads with why'), though there is no explicit error-recovery feedback loop to justify a 5.

4 / 5

Progressive Disclosure

Under 50 lines with no need for external references, and the content is cleanly organized into well-signaled ## Write and ## Publish sections, satisfying the simple-skill exception.

5 / 5

Total

18

/

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, third-person description that clearly answers both what and when with natural trigger phrases. Minor room to broaden the enumerated concrete actions beyond 'drafts and reviews'.

DimensionReasoningScore

Specificity

Names the domain (GitHub PR descriptions) and two concrete actions ('Drafts and reviews'), but does not enumerate several specific actions, matching the 1-2 concrete actions anchor rather than the 'several' of a 4.

3 / 5

Completeness

It explicitly states what the skill does ('Drafts and reviews GitHub pull request descriptions for the eve repository') and when to use it with concrete trigger phrases via an explicit 'Use when' clause.

5 / 5

Trigger Term Quality

Good natural-term coverage with 'opening, updating, or reviewing a PR' and 'summarizing a branch for reviewers' plus the PR/pull request synonym pair, but it stops short of the comprehensive synonym-and-extension breadth of a 5.

4 / 5

Distinctiveness Conflict Risk

It carves a clear niche—PR description drafting/review for a specific repo—with distinct triggers and minimal overlap with other skills.

5 / 5

Total

17

/

20

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

Validation for skill structure

No warnings or errors.

Repository
vercel/eve
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.