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.

64

Quality

77%

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

85%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is a well-sequenced, highly actionable pipeline with strong validation checkpoints and clean sectioning. Its only weakness is mild verbosity in the GitLab-template and skills-guard sections that could be tightened.

Suggestions

Trim the GitLab template-mapping sub-steps (sections 1-5) into a more compact list; several caveats repeat guidance already in the Description rules.

Condense the skills-guard Step 0, which is repo-specific and adds length not relevant to most invocations, or move it to a reference.

Remove duplicated guidance between 'Important' and earlier steps (e.g. failing-checks rule appears in both Step 4 and Important).

DimensionReasoningScore

Conciseness

The body is mostly efficient with executable commands and minimal concept explanation, but some sections (the GitLab template mapping and skills-guard steps) could be tightened and feel slightly padded with caveats.

2 / 3

Actionability

Provides concrete, copy-paste-ready commands (git, gh pr create, glab mr create, make skills-guard), exact code fences for the structured body, and specific provider-assembly rules with clear flags.

3 / 3

Workflow Clarity

A clear numbered 0-9 sequence with explicit validation checkpoints (self-review, run checks, ask user before proceeding on failing checks, draft-when-unverified feedback loop) matches the top anchor.

3 / 3

Progressive Disclosure

No bundle files exist and none are needed; content is organized into clearly headed sections (Steps, Description rules, Provider assembly, Creating the PR/MR) with concise navigation, satisfying the simple-skill allowance.

3 / 3

Total

11

/

12

Passed

Description

70%Weight 40%Scale 1-3

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 distinctive, with concrete actions and a clear niche, but it omits an explicit 'Use when...' trigger clause and natural user phrasings, which caps completeness and trigger term quality.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when opening a pull request or merge request, or when the user asks to create/open/file a PR or MR.'

Include natural user phrasings like 'open a pull request', 'create a merge request', or 'file a PR' alongside 'GitHub gh / GitLab glab'.

Consider trimming the parenthetical detail about TL;DR/change table/mermaid to keep the description scannable.

DimensionReasoningScore

Specificity

Lists multiple concrete actions: 'runs self-review + checks', 'writes a structured description (TL;DR, change table, mermaid flow)', and 'adapts the project's .gitlab/merge_request_templates template', matching the top anchor.

3 / 3

Completeness

It clearly answers what the skill does but has no 'Use when...' trigger clause, so per the guidelines completeness is capped at 2.

2 / 3

Trigger Term Quality

Names natural terms like 'PR/MR', 'GitHub', 'GitLab', 'self-review', 'checks', and 'draft', but lacks common variations users actually say like 'open a pull request', 'merge request', or 'create a PR'.

2 / 3

Distinctiveness Conflict Risk

The VCS-aware PR/MR pipeline niche with template adaptation is a clear, distinct domain unlikely to conflict with other skills.

3 / 3

Total

10

/

12

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.