CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

pr

Open a GitHub PR targeting the correct branch with the project template

Quality

80%

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

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/pr/SKILL.md
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.

The body is an exemplary lean, executable workflow: concrete commands, a clear sequence, an explicit validation gate, and well-organized sections with no padding. The only refinement worth making is a brief error-recovery note for failing checks.

DimensionReasoningScore

Conciseness

The body is 44 lean lines: every instruction is project-specific (base branch, `make ci`, `gh pr create --base main --fill-first`, template sections) with zero padding or explanation of concepts Claude already knows. This matches the 5 anchor 'Lean and efficient; every token earns its place'.

5 / 5

Actionability

The guidance is fully executable with copy-paste-ready commands (`make ci`, `git push -u origin HEAD`, `gh pr create --base main --fill-first`) plus a concrete enumeration of the template sections to complete. It covers the common case end-to-end, matching the 5 anchor.

5 / 5

Workflow Clarity

The four steps are clearly sequenced with an explicit validation gate ("Do not open a PR with failing lint/tests") and honesty requirements for the Verification section. It falls short of the 5 anchor because there is no error-recovery feedback loop (e.g., what to do when `make ci` fails) — a minor validation gap characteristic of the 4 anchor.

4 / 5

Progressive Disclosure

This is a sub-50-line single-task skill with well-organized sections (## Steps, ## Notes) and no need for external reference files; the only link, the PR template at [.github/PULL_REQUEST_TEMPLATE.md](../../../.github/PULL_REQUEST_TEMPLATE.md), is a clearly signaled one-level project file the skill must interact with. Per the rubric's simple-skill guideline this merits a 5.

5 / 5

Total

19

/

20

Passed

Description

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

The description is concise and names concrete actions with a clear 'what', but it lacks any 'when to use' guidance and misses natural trigger variations like 'pull request'. It is serviceable but would be substantially improved with an explicit trigger clause.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to open, create, or submit a pull request or PR."

Include the spelled-out term "pull request" alongside "PR" so the description matches users who say either form.

Optionally mention that the skill fills in the PR template sections and runs checks first, making the capability coverage more comprehensive.

DimensionReasoningScore

Specificity

The description lists several concrete actions — "Open a GitHub PR", "targeting the correct branch", "with the project template" — each naming a specific operation rather than vague domain language. It falls short of a 5 because coverage is not comprehensive: it omits filling out the template sections and the pre-PR checks, but it clearly exceeds the 3 anchor's '1-2 concrete actions' threshold.

4 / 5

Completeness

The 'what' is clear (open a GitHub PR on the correct branch using the project template), but there is no 'when' clause or equivalent trigger guidance anywhere in the description. Per the judging guidelines a missing 'Use when...' clause caps completeness at 3, and this matches the 3 anchor exactly.

3 / 5

Trigger Term Quality

It contains relevant keywords ("GitHub PR", "branch", "template") but misses the common variations users naturally say, most notably "pull request" spelled out, plus "create/submit a PR". This matches the anchor 'Some relevant keywords but missing common variations or synonyms' — not a 4, since a phrase as basic as "pull request" is absent alongside the abbreviation.

3 / 5

Distinctiveness Conflict Risk

The niche is fairly distinct — PR creation against a specific base branch with a project template — with concrete triggers like "GitHub PR" and "correct branch" that would not fire for unrelated skills. Minor overlap risk remains with generic PR/review-related skills, keeping it below the 5 anchor's 'clear niche with minimal conflict risk'.

4 / 5

Total

14

/

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

relative_links

Relative link issues: 1 suspicious

Warning

Total

15

/

16

Passed

Repository

EverMind-AI/EverOS

Path

.claude/skills/pr/SKILL.md

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.