CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

create-pr

Orchestrates the full PR lifecycle: merge upstream, self code review locally, create a standard PR, monitor, and iterate on fixes. Can also monitor and iterate on an existing PR. Input: [--push-remote <fork>] [--upstream-remote <remote>] [--base <branch>] [--merge] [--mode automatic|interactive] [--review-lens instructions|agnostic|both] [--pr <number>]

Quality

79%

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

Fix and improve this skill with Tessl

tessl review fix ./.github/skills/create-pr/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

81%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 thorough, well-sequenced orchestrator skill with highly executable commands, explicit validation checkpoints, feedback loops, and clear exit conditions. The only weaknesses are minor: some repetition around --pr handling, a placeholder in the gh pr create block, and inline bulk that could be split into reference files.

DimensionReasoningScore

Conciseness

The body is dense and operational — no explanations of concepts Claude already knows, and every section carries procedure (commands, flags, decision rules). Minor trimmable redundancy exists: the '--pr' / '--review-lens is ignored' behavior is stated in the Input table, the Input prose, and the Step 1 callout, and the reviewer-pipeline detail could be slightly compressed.

4 / 5

Actionability

Guidance is largely copy-paste ready: exact git/gh commands with --jq filters, a complete GraphQL query, commit-message templates, and the gh pr create invocation. Minor gaps remain — Step 4's title/body file creation is a placeholder comment ('# ... create pr-title.txt and pr-body.md ...') and 'session-local storage (e.g. a review_threads SQL table)' leaves the persistence mechanism to the reader.

4 / 5

Workflow Clarity

Steps 1–6 are clearly sequenced with an upfront input-gathering phase, a confirmation checklist ('Here's the plan... Ready to proceed?'), explicit validation checkpoints ('Always run the Quality commands... Iterate until they pass — do not push broken code'), feedback loops for CI/test failures, and explicit exit conditions including a 3-failure circuit breaker. Interactive/automatic mode gating is unambiguous.

5 / 5

Progressive Disclosure

The single-file skill is well organized with clearly signaled step sections, and external pointers (.github/instructions/pr-labels.md, .github/copilot-instructions.md) are one level deep and clearly named. However, sizable self-contained blocks (the reviewer-ranking pipeline in 1d, the GraphQL thread query in Step 6) are inlined in a ~470-line SKILL.md and could arguably live in reference files, keeping it just short of ideal structure.

4 / 5

Total

17

/

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 strong, specific, third-person description that clearly communicates the what (end-to-end PR lifecycle orchestration, including an existing-PR mode). Its main weakness is the absence of any 'Use when...' trigger clause, which caps completeness, and slightly thin natural-language trigger synonyms.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to create/open/submit a pull request, or wants an existing PR monitored and fixed through review.'

Include natural synonyms such as 'pull request', 'open a PR', and 'PR feedback' alongside 'PR' to broaden trigger-term coverage.

Trim the raw CLI flag list ('Input: [--push-remote <fork>] ...') or move it to the argument-hint field only, since flag syntax is not natural trigger language for the description.

DimensionReasoningScore

Specificity

The description lists multiple specific concrete actions — 'merge upstream, self code review locally, create a standard PR, monitor, and iterate on fixes' — giving comprehensive coverage of the PR lifecycle in third-person voice ('Orchestrates'). No vague filler or abstract language is present.

5 / 5

Completeness

The 'what' is clearly answered (full PR lifecycle orchestration plus the existing-PR path via '--pr <number>'), but there is no 'Use when...' clause or equivalent explicit trigger guidance telling Claude when to invoke this skill. Per the judging guidelines, a missing 'Use when...' clause caps completeness at 3.

3 / 5

Trigger Term Quality

Good natural keywords users would say: 'PR', 'create a standard PR', 'code review', 'monitor', 'review comments', 'CI failures' (implied via iterate on fixes). However, common variations like 'pull request', 'open a PR', or 'submit a PR' are missing, and the 'Input:' line is CLI-flag jargon rather than trigger phrasing.

4 / 5

Distinctiveness Conflict Risk

The PR-creation-and-shepherding niche is clear and mostly distinct ('create a standard PR, monitor, and iterate'), with minimal overlap risk. Minor overlap remains with closely related skills it orchestrates (code-review, monitor-pr, merge-and-resolve), which a user might invoke directly instead.

4 / 5

Total

16

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 3 missing, 1 suspicious

Warning

Total

14

/

16

Passed

Repository

BabylonJS/Babylon.js

Path

.github/skills/create-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.