CtrlK
BlogDocsLog inGet started
Tessl Logo

github-pr-workflow

Prepare a GitHub pull request from a feature branch — branch hygiene, commit shape, title/body, verification notes, screenshots for UI work, and replies to review comments.

68

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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

The body is concise, actionable, and well-sequenced with explicit validation checkpoints and a merge checklist. As an instruction-only skill it provides specific, copy-paste-ready guidance throughout.

DimensionReasoningScore

Conciseness

Lean and free of padding; lines like 'Imperative mood, under 70 characters.' and 'No trailing period.' assume Claude's competence and never explain concepts it already knows.

3 / 3

Actionability

Gives concrete, executable guidance — a copy-paste PR-body template, 'under 70 characters', and a worked contrast ('Allow CSV export from reports table' beats 'Update reports.tsx') — rather than abstract direction.

3 / 3

Workflow Clarity

Sequences the full PR lifecycle (branch hygiene → title → body → verification → replies → merge checklist) with explicit validation checkpoints such as 'Confirm tests, typecheck, and lint pass locally' and 'All required checks green.'

3 / 3

Progressive Disclosure

A focused single-file skill with clearly labeled sections and no nested references; the organization provides easy navigation without requiring external bundle files.

3 / 3

Total

12

/

12

Passed

Description

67%

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 specific and distinctive, clearly listing the concrete PR-preparation actions it covers. Its weakness is the absence of an explicit 'Use when...' trigger clause and thinner coverage of common phrasings like 'PR'.

Suggestions

Append a 'Use when...' clause, e.g. 'Use when opening a GitHub pull request or responding to review comments on one.'

Add common trigger variants such as 'PR', 'open a PR', and 'code review' so users' natural phrasings match.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'branch hygiene, commit shape, title/body, verification notes, screenshots for UI work, and replies to review comments' — rather than naming only a domain.

3 / 3

Completeness

Clearly answers what the skill does but lacks an explicit 'Use when...' trigger clause; per the judging guideline, a missing when-clause caps completeness at 2.

2 / 3

Trigger Term Quality

Contains natural terms ('GitHub pull request', 'feature branch', 'review comments', 'screenshots') but omits common variations like 'PR', 'open a PR', or 'code review' that users would actually say.

2 / 3

Distinctiveness Conflict Risk

The GitHub-PR-preparation niche is well-scoped with distinct triggers, making it unlikely to fire for unrelated skills.

3 / 3

Total

10

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
paperclipai/paperclip
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.