pr-creator

Use this skill when asked to create a pull request (PR). It ensures all PRs follow the repository's established templates and standards.

1.10x

Quality

58%

Does it follow best practices?

Impact

94%

1.10x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./.gemini/skills/pr-creator/SKILL.md

Quality

Discovery

40%

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 identifies its core purpose (creating pull requests) and includes a 'Use when' trigger, but it is too vague about what concrete actions it performs. It lacks specific capabilities (e.g., filling templates, generating descriptions, linking issues) and misses common trigger term variations. The description would benefit from more concrete action verbs and broader keyword coverage.

Suggestions

Add specific concrete actions the skill performs, e.g., 'Generates PR titles, fills in description templates, links related issues, and adds appropriate labels.'

Expand trigger terms to include variations like 'merge request', 'open a PR', 'submit changes for review', 'gh pr create'.

Rephrase to third person voice describing capabilities, e.g., 'Creates pull requests following repository templates and standards. Use when...'

Dimension	Reasoning	Score
Specificity	The description says 'create a pull request' and 'follows templates and standards' but does not list any concrete actions beyond that. It lacks specifics like 'generates PR title, fills in description template, adds labels, links issues'.	1 / 3
Completeness	It has a 'when' clause ('when asked to create a pull request') and a weak 'what' ('ensures PRs follow templates and standards'). However, the 'what' is vague and the description uses second-person-adjacent 'Use this skill' phrasing rather than clearly stating capabilities. The 'when' is present but the 'what' is insufficiently detailed.	2 / 3
Trigger Term Quality	Includes 'pull request' and 'PR' which are natural trigger terms users would say. However, it misses common variations like 'merge request', 'open a PR', 'submit PR', 'gh pr create', or related terms like 'code review'.	2 / 3
Distinctiveness Conflict Risk	It's specific to pull request creation which narrows the domain, but 'follows templates and standards' is vague enough that it could overlap with general code review or git workflow skills.	2 / 3
	Total	7 / 12 Passed

Implementation

77%

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

This is a solid, actionable skill with a well-sequenced workflow that includes important safety rails and validation checkpoints. The concrete bash commands and step-by-step structure make it immediately usable. Minor improvements could be made in conciseness by trimming redundant explanations and in progressive disclosure by better organizing supplementary content.

Suggestions

Trim the Principles section since its points are already embedded as CRITICAL notes in the workflow steps, or reduce it to a single-line reminder.

Tighten step 5 by removing explanations of how checklists work (Claude already knows markdown checkbox syntax) and focusing only on the repository-specific guidance.

Dimension	Reasoning	Score
Conciseness	The content is mostly efficient but includes some unnecessary elaboration, such as explaining what checklists are and how to mark them, and the Principles section restates things already covered in the workflow. Some tightening is possible.	2 / 3
Actionability	Every step includes concrete, executable bash commands (git, gh CLI). The workflow provides specific file paths to check for templates, exact command syntax with flags like --body-file, and clear examples of conventional commit format.	3 / 3
Workflow Clarity	The 8-step workflow is clearly sequenced with explicit validation checkpoints: branch verification before starting, git status check before committing, preflight script before pushing, and a critical safety rail double-check before push. There's a clear feedback loop at step 6 (fix issues if checks fail).	3 / 3
Progressive Disclosure	The content is well-structured with clear headings and a logical flow, but it's a moderately long single file with no references to external documents. The Principles section could be integrated into the workflow steps rather than repeated at the end, and the template-handling details could potentially be split out.	2 / 3
	Total	10 / 12 Passed

Validation

100%

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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: google-gemini/gemini-cli
Commit: 0758a5e

Reviewed: 3 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.