CtrlK
BlogDocsLog inGet started
Tessl Logo

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>]

65

Quality

80%

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

88%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 content is highly actionable with a clearly sequenced, validation-backed workflow and concrete executable commands throughout. Its only weakness is minor verbosity and some detailed procedures inlined rather than split into reference files.

DimensionReasoningScore

Conciseness

The body is dense with concrete commands and avoids explaining concepts Claude already knows; the explanatory callouts (--no-pager, three-dot diff, --body-file) are genuine non-obvious gotchas, though a few could be trimmed.

4 / 5

Actionability

Provides copy-paste-ready bash, gh API, and GraphQL commands with exact flags covering the common cases; the single flagged placeholder for temp-file creation is an explicit handoff rather than vague guidance.

5 / 5

Workflow Clarity

Steps 1–6 are clearly sequenced with explicit validation checkpoints ('Always run the Quality commands before pushing', 'Iterate until they pass'), feedback loops, and concrete exit conditions ('Same issue fails 3 times → stop').

5 / 5

Progressive Disclosure

Good section structure with clearly signaled one-level-deep references (pr-labels.md, copilot-instructions.md) and invoked sub-skills; no bundle files exist, and some detailed sub-procedures (reviewer ranking, GraphQL response posting) are inlined that could live in reference files.

4 / 5

Total

18

/

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.

The description is specific and distinct, clearly conveying what the skill does across the PR lifecycle, but it lacks an explicit 'Use when...' trigger clause which caps its completeness.

Suggestions

Add an explicit 'Use when...' clause naming natural trigger phrases (e.g. 'Use when creating a pull request, preparing a PR for review, or monitoring an existing PR').

Include the synonym 'pull request' alongside 'PR' to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'merge upstream, self code review locally, create a standard PR, monitor, and iterate on fixes' — giving comprehensive coverage of the PR lifecycle.

5 / 5

Completeness

The 'what' is clearly answered, but there is no explicit 'Use when...' trigger clause, so per the rubric completeness is capped at 3.

3 / 5

Trigger Term Quality

Natural terms like 'PR', 'create a PR', 'code review', 'merge', 'monitor' are present, but synonyms such as 'pull request' and common phrasings are missing.

4 / 5

Distinctiveness Conflict Risk

A clear niche (PR lifecycle orchestration) with distinct triggers; only minor overlap with the sub-skills (code-review, monitor-pr) it explicitly invokes.

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.

Validation14 / 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
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.