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.

67

Quality

81%

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

The canonical home for this skill is create-pr in AndreJorgeLopes/devflow

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 clear, validated workflow and clean sectioning; its only weakness is minor over-explanation and a longish inline GitLab-adaptation section. No bundle files exist, so progressive disclosure is scored against the single-file structure.

DimensionReasoningScore

Conciseness

The body is dense, command-driven, and assumes Claude's competence, but includes a few rationale asides (e.g. 'Em-dashes read as machine-written and are a hard no.') that could be trimmed, keeping it just shy of fully lean.

4 / 5

Actionability

Provides copy-paste-ready commands with exact flags across GitHub, GitLab, and unknown providers (git push, gh pr create --body-file --draft, glab mr create --target-branch), plus a concrete body template, covering the common cases fully.

5 / 5

Workflow Clarity

A clearly numbered 0-9 sequence with explicit validation checkpoints (self-review, checks, approval gate) and a draft-when-unverified feedback loop, plus a checklist, for destructive/batch push-and-create operations.

5 / 5

Progressive Disclosure

Well-organized into clear sections (Steps, Description rules, Provider assembly, Creating the PR/MR, Important) in a single file with no bundle files needed; references to CLAUDE.md are one-level and clearly signaled, but the GitLab template-adaptation block is fairly long and could be split out.

4 / 5

Total

18

/

20

Passed

Description

75%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, action-rich, and clearly distinct, but it omits an explicit 'Use when...' trigger clause, which the rubric uses to cap completeness at 3. Adding a trigger phrase would raise the completeness dimension.

Suggestions

Append an explicit trigger clause such as 'Use when the user asks to open/create a pull request or merge request, or wants to package a branch of changes into a PR/MR.'

Spell out 'pull request' and 'merge request' at least once alongside the PR/MR abbreviations to improve natural trigger-term coverage.

DimensionReasoningScore

Specificity

Lists multiple concrete actions, self-review, checks, a structured description with TL;DR/change-table/mermaid/verification, GitLab template adaptation, and draft-on-incomplete behavior, giving comprehensive coverage of the pipeline.

5 / 5

Completeness

The 'what' is clearly and concretely stated, but there is no 'Use when...' clause or equivalent explicit trigger guidance, so per the rubric completeness caps at 3.

3 / 5

Trigger Term Quality

Good natural keyword coverage (PR/MR, GitHub/GitLab, gh/glab) that users would say, but the full phrases 'pull request'/'merge request' are abbreviated rather than spelled out, leaving a few natural terms missing.

4 / 5

Distinctiveness Conflict Risk

It carves a clear niche (full PR/MR creation pipeline, VCS-aware, with template adaptation) with distinct triggers and minimal overlap with adjacent skills like commit-message generation.

5 / 5

Total

17

/

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.