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

82%

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

93%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.

An exemplary instruction-only skill body: lean, highly actionable, with a clear lifecycle sequence, explicit checklists, and a closing anti-patterns section that sharpens judgment. The only gap is the absence of failure-path guidance (rebase conflicts, failing checks), which keeps workflow clarity at 4.

DimensionReasoningScore

Conciseness

The body is lean and directive throughout — it never explains what a PR is or how Git works, and every line prescribes behavior ('Imperative mood, under 70 characters', 'No trailing period'), so every token earns its place.

5 / 5

Actionability

Concrete, copy-paste-ready guidance dominates: a complete fenced PR body template with Summary/Implementation notes/Verification/Risk sections, contrastive title examples ('Allow CSV export from reports table' beats 'Update reports.tsx'), and exact rules. Per the scoring notes, absence of code in an instruction-only skill is not penalized when guidance is this actionable.

5 / 5

Workflow Clarity

A clear lifecycle sequence (branch hygiene → title → body → verification → review replies → merge checklist) with checkpoints ('Confirm tests, typecheck, and lint pass locally', the merge checklist) and a review feedback loop (push fixes, re-request review). It falls short of 5 only because there are no error-recovery branches for failures like rebase conflicts or red CI checks.

4 / 5

Progressive Disclosure

The skill is a single self-contained file with well-organized sections (When to use / When not to use / per-phase sections / Anti-patterns) and no external references needed — no references/, scripts/, or assets/ bundles exist, so the well-organized-sections bar for a 5 is met.

5 / 5

Total

19

/

20

Passed

Description

71%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 specific, well-scoped description with concrete action enumeration and natural trigger terms, but it lacks any explicit 'Use when...' clause, which caps completeness and leaves triggering to inference. Adding a when-to-use sentence with synonyms like 'PR' and 'code review' would raise it to the top level.

Suggestions

Add an explicit trigger clause, e.g. 'Use when opening a PR, updating a stale PR, or responding to code review comments on a GitHub pull request.'

Include common user synonyms such as 'PR' and 'code review' alongside 'pull request' and 'review comments' to broaden natural trigger coverage.

State the boundary against adjacent skills (e.g., commit-message generation or reviewing others' PRs) to reduce conflict risk.

DimensionReasoningScore

Specificity

The description enumerates six concrete actions — 'branch hygiene, commit shape, title/body, verification notes, screenshots for UI work, and replies to review comments' — giving comprehensive coverage of PR preparation with no gaps, matching the anchor for multiple specific concrete actions.

5 / 5

Completeness

It clearly answers 'what' (prepare a PR: branch hygiene, commit shape, title/body, etc.) but contains no 'Use when...' clause or equivalent explicit trigger guidance — the 'when' is only weakly implied by 'from a feature branch', which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Natural terms like 'GitHub pull request', 'commit', 'review comments', and 'screenshots' are present, but common user phrasings such as 'PR', 'open a PR', or 'code review feedback' are missing, so keyword coverage is good but not comprehensive.

4 / 5

Distinctiveness Conflict Risk

The PR-preparation niche is clear and mostly distinct, but 'commit shape' and 'replies to review comments' create minor overlap risk with closely related commit-message and code-review skills rather than the minimal-conflict anchor.

4 / 5

Total

16

/

20

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.

Validation — 15 / 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.