CtrlK
BlogDocsLog inGet started
Tessl Logo

create-pr

Full PR/MR creation pipeline. VCS-aware (GitHub `gh` / GitLab `glab`), runs self-review + checks, and writes a structured description (TL;DR, change table, mermaid flow, honest verification status, no em-dashes). On GitLab it adapts the project's `.gitlab/merge_request_templates` template, filling its sections and appending only the extras it lacks. Opens as a draft when verification is incomplete.

66

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 ./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 body is highly actionable with a well-sequenced, validation-rich workflow appropriate to an irreversible operation, and is mostly token-efficient with good sectioning; its main gap is minor over-explanation and inlined detail that progressive disclosure could offload.

DimensionReasoningScore

Conciseness

The body is dense and task-oriented with executable commands, but a few justifications (e.g. 'Em-dashes read as machine-written and are a hard no' and the skills-guard preamble) could be trimmed without losing guidance.

4 / 5

Actionability

Provides copy-paste-ready executable commands throughout: 'git log --oneline main..HEAD', 'devflow check', 'gh pr create --title ... --body-file /tmp/devflow-pr-body.md', and 'glab mr create ... --target-branch ...', covering the common GitHub and GitLab cases.

5 / 5

Workflow Clarity

A clearly sequenced 0-9 pipeline with explicit validation gates (self-review in step 2, checks in step 3, the 'fix first or proceed' feedback loop in step 4, approval gate in step 7), draft-when-unverified logic, and a checklist block for an irreversible operation.

5 / 5

Progressive Disclosure

No bundle files exist, so navigation is by section headers alone (Steps, Description rules, Provider assembly, Creating the PR/MR, Important); the file is well-organized but the detailed GitLab template-adaptation block is inlined where a one-level reference could keep the overview leaner.

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 highly specific and action-rich with a clear niche, but it lacks an explicit 'Use when...' trigger clause, which caps completeness and slightly weakens trigger-term coverage and distinctiveness.

Suggestions

Add an explicit 'Use when...' clause naming natural triggers, e.g. 'Use when creating a pull request or merge request, opening a PR/MR, or finalizing a branch for review.'

Spell out 'pull request' and 'merge request' alongside 'PR/MR' to broaden natural keyword coverage.

Lead with the trigger phrase before the capability list so the 'when' is as explicit as the 'what'.

DimensionReasoningScore

Specificity

Lists multiple concrete actions: 'runs self-review + checks', 'writes a structured description (TL;DR, change table, mermaid flow, honest verification status, no em-dashes)', 'adapts the project's .gitlab/merge_request_templates template, filling its sections and appending only the extras it lacks', and 'Opens as a draft when verification is incomplete'.

5 / 5

Completeness

The 'what' is clear and detailed, but there is no explicit 'Use when...' trigger clause; the 'when' is only weakly implied by 'PR/MR creation pipeline', which per the judging guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

Good keyword coverage with 'PR/MR creation', 'GitHub', 'GitLab', 'gh', 'glab', 'self-review', 'checks', but the spelled-out natural phrases 'pull request' and 'merge request' are absent, leaving a few common terms missing.

4 / 5

Distinctiveness Conflict Risk

It carves a clear niche (VCS-aware PR/MR creation with template adaptation and draft logic), but without explicit trigger phrases it has minor overlap risk with closely related commit-message or self-review skills.

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

15

/

16

Passed

Repository
AndreJorgeLopes/devflow
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.