CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

72

1.10x
Quality

58%

Does it follow best practices?

Impact

94%

1.10x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

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

Quality

Content

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-structured multi-step workflow that includes important safety rails and validation checkpoints. Its main weakness is minor verbosity—the Principles section is redundant with inline guidance, and some commentary could be trimmed. The executable commands and clear sequencing make this highly usable.

Suggestions

Remove or condense the Principles section, as its points (never push to main, follow the template, check boxes accurately) are already stated inline within the workflow steps.

Trim minor verbal padding like 'This is your highest priority' and 'It exists for a reason' to improve token efficiency.

DimensionReasoningScore

Conciseness

The skill is mostly efficient but includes some unnecessary verbosity—e.g., the Principles section restates what's already embedded in the workflow steps, and some inline commentary ('It exists for a reason') adds no value for Claude. The workflow steps themselves are reasonably tight.

2 / 3

Actionability

Every step includes concrete, executable bash commands (git, gh CLI). The guidance is specific about file paths to check for templates, exact flags to use (--body-file), and the temp file pattern to avoid shell escaping issues. This is copy-paste ready.

3 / 3

Workflow Clarity

The 8-step workflow is clearly sequenced with explicit validation checkpoints: checking current branch before proceeding, running `git status` to verify commits, running `npm run preflight` before pushing, and a double-check safety rail before push. There are clear feedback loops (if checks fail, address issues before proceeding).

3 / 3

Progressive Disclosure

The content is well-organized with clear sections (Workflow, Principles), but everything is inline in a single file. For a skill of this length (~80 lines of content), this is acceptable, but the Principles section could be folded into the workflow steps to reduce redundancy. No bundle files exist, so there's no progressive disclosure to external references.

2 / 3

Total

10

/

12

Passed

Description

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 a clear trigger scenario (creating pull requests) but lacks specificity about what concrete actions the skill performs. It uses second-person voice ('Use this skill when asked') which is borderline but acceptable. The description would benefit significantly from listing specific capabilities and adding more trigger term variations.

Suggestions

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

Expand trigger terms to include variations like 'merge request', 'open a PR', 'submit changes for review', 'push changes upstream'.

Rewrite in third person voice, e.g., 'Creates pull requests following repository templates and standards. Use when...'

DimensionReasoningScore

Specificity

The description says 'create a pull request' and 'follows templates and standards' but does not list any concrete actions beyond creating a PR. It lacks specifics like 'generates PR title, fills in description template, adds labels, links issues.'

1 / 3

Completeness

The 'when' is present ('when asked to create a pull request') but the 'what' is weak—it only vaguely says it 'ensures PRs follow templates and standards' without specifying what concrete steps or outputs are involved. The 'Use when' equivalent exists but the what-it-does portion is underdeveloped.

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 changes', or 'code review'.

2 / 3

Distinctiveness Conflict Risk

It's somewhat specific to PR creation, but could overlap with general git workflow skills, code review skills, or repository management skills. The mention of 'templates and standards' adds some distinction but is still fairly broad.

2 / 3

Total

7

/

12

Passed

Validation

100%

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

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
google-gemini/gemini-cli
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.