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.

84

1.10x
Quality

77%

Does it follow best practices?

Impact

94%

1.10x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.gemini/skills/pr-creator/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

92%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 body is a tight, executable, well-sequenced workflow with validation feedback loops and safety rails, organized into clean sections with no external references needed.

DimensionReasoningScore

Conciseness

Lean and free of concept-overexplaining (no preamble on what a PR or git is), with minor trimmable redundancy such as "Verify that all intended changes are committed" restating the command that follows.

4 / 5

Actionability

Fully executable, copy-paste-ready commands throughout (git branch/checkout/add/commit/push, npm run preflight, gh pr create --body-file), with the multi-line body handled via the temp-file pattern.

5 / 5

Workflow Clarity

Clear 8-step sequence with explicit validation checkpoints and a feedback loop (run preflight, address failures before proceeding) plus branch-verification safety rails before the destructive push/PR steps.

5 / 5

Progressive Disclosure

Self-contained single file with no bundle directories present and well-organized sections (Workflow, Principles); no external references are needed, so the clear in-file structure satisfies progressive disclosure.

5 / 5

Total

19

/

20

Passed

Description

62%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 answers both what and when with a natural trigger term, but the capability statement is generic and lacks a range of specific actions or trigger synonyms.

Suggestions

List concrete actions the skill performs (e.g., locates PR templates, drafts descriptions from templates, runs preflight checks, pushes branch, opens the PR via gh) instead of the generic "ensures all PRs follow templates and standards."

Add natural trigger variations such as "open a PR" and "submit a pull request" alongside "create a pull request (PR)."

Tighten the "what" to specify the template-adherence and safety-rail behavior (never pushing to main) that distinguishes this skill.

DimensionReasoningScore

Specificity

Names the domain and one concrete action ("create a pull request (PR)") but the rest ("ensures all PRs follow the repository's established templates and standards") is generic, not a list of several specific actions.

3 / 5

Completeness

Both "what" (ensures PRs follow templates/standards) and an explicit "when" ("Use this skill when asked to create a pull request") are present, though the "what" is somewhat generic.

4 / 5

Trigger Term Quality

"pull request (PR)" is a natural user phrase, but common variations like "open/submit a PR" and related synonyms are absent.

3 / 5

Distinctiveness Conflict Risk

"create a pull request (PR)" is a clear niche trigger with minimal conflict risk, overlapping only slightly with general git/commit skills.

4 / 5

Total

14

/

20

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.

Validation16 / 16 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.