Tessl • The package manager for agent skills

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.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

92%

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 and concise, with a clear numbered workflow, executable commands, and explicit validation/draft gating. Progressive disclosure is the weakest area: content is well-organized but monolithic with no external bundle files to offload detail.

Suggestions

Split the large Provider assembly / GitLab template-adaptation block into a referenced file (e.g. references/gitlab-templates.md) and keep a concise summary plus a clearly-signaled one-level-deep link in SKILL.md.

Consider extracting the full GitHub/GitLab body templates into a references/ file so the main body stays a lean overview with well-signaled navigation.

Dimension	Reasoning	Score
Conciseness	The body is dense yet lean: it assumes Claude knows what a PR/MR is and devotes every line to skill-specific decisions (provider detection, draft logic, template preservation), avoiding concept-fluff Claude already knows.	3 / 3
Actionability	Provides fully executable, copy-paste-ready commands with flags explained — 'gh pr create --title "<title>" --body-file /tmp/devflow-pr-body.md', 'glab mr create ... --target-branch <default-branch> --yes', 'git push -u origin HEAD' — not pseudocode.	3 / 3
Workflow Clarity	A clearly numbered 0-9 sequence with explicit validation checkpoints: step 4 gates on self-review/checks surfacing issues ('Never open a PR/MR with failing checks unless... explicitly approves') and draft-when-unverified logic ties an explicit condition to the final create step.	3 / 3
Progressive Disclosure	The body is well-sectioned (Steps, Description rules, Provider assembly, Creating) but at ~150 lines it is monolithic with no one-level-deep bundle references — provider-assembly details and templates are inline rather than split into reference files, and the only cross-refs point to CLAUDE.md rather than skill bundle files.	2 / 3
	Total	11 / 12 Passed

Description

67%

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 well-differentiated, naming concrete pipeline actions and provider-aware behavior. Its main weakness is the absence of an explicit 'Use when...' trigger clause, leaving the 'when to use' half only implied.

Suggestions

Add an explicit trigger clause, e.g. 'Use when creating a pull request or merge request, opening a PR/MR, or when the user asks to submit a branch for review.'

Broaden natural trigger terms to include 'pull request', 'merge request', and 'open a PR' alongside the existing PR/MR and provider keywords.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions: 'runs self-review + checks', 'writes a structured description (TL;DR, change table, mermaid flow...)', 'adapts the project's .gitlab/merge_request_templates template', 'Opens as a draft when verification is incomplete' — none are vague.	3 / 3
Completeness	Clearly answers 'what' the skill does, but 'when' is only implied — there is no explicit 'Use when...' clause, which per the judging guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	Includes relevant terms ('PR/MR', 'GitHub', 'GitLab', 'gh', 'glab') but is capability-prose rather than natural trigger phrasing a user would say, and omits common variations like 'pull request', 'merge request', or 'open a PR'.	2 / 3
Distinctiveness Conflict Risk	Occupies a clear niche (VCS-aware PR/MR creation pipeline with GitLab template adaptation) and is unlikely to trigger for or conflict with other skills.	3 / 3
	Total	10 / 12 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 2 missing	Warning

	Total	15 / 16 Passed

Repository: AndreJorgeLopes/devflow
Commit: 9556c94

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.