CtrlK
BlogDocsLog inGet started
Tessl Logo

create-pr

Push the current branch and create a pull request against docker/docs. Use after changes are committed and reviewed. "create a PR", "submit the fix", "open a pull request for this".

79

Quality

100%

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

SKILL.md
Quality
Evals
Security

Quality

Content

100%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.

A well-structured, executable workflow with concrete commands, explicit validation checkpoints, and clean sectioning. It assumes Claude's competence and avoids unnecessary explanation throughout.

DimensionReasoningScore

Conciseness

The body is command-first and lean; it does not explain git/PR concepts Claude already knows, and the surrounding prose is actionable rather than padded.

3 / 3

Actionability

Every step is backed by fully executable git and gh commands with concrete flags and clearly marked placeholders, making the guidance copy-paste ready.

3 / 3

Workflow Clarity

A clear five-step sequence (verify, push, create, label/review, report) with explicit validation checkpoints and stop conditions, including duplicate-PR and reviewer-assignment feedback loops.

3 / 3

Progressive Disclosure

A single self-contained file organized into well-labeled sections with no nested references; content is appropriately inline for a single-task workflow skill.

3 / 3

Total

12

/

12

Passed

Description

100%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.

A tightly written description that states concrete actions, an explicit use-when clause, and natural trigger phrases, all scoped to a single repo. It hits every dimension the rubric rewards.

DimensionReasoningScore

Specificity

Names multiple concrete actions ("Push the current branch and create a pull request") and a specific target ("against docker/docs"), matching the anchor that lists several specific concrete actions.

3 / 3

Completeness

Explicitly answers both what (push branch and create a PR against docker/docs) and when ("Use after changes are committed and reviewed"), with explicit quoted triggers.

3 / 3

Trigger Term Quality

Includes natural phrases a user would actually say — "create a PR", "submit the fix", "open a pull request for this" — giving good coverage of natural trigger terms.

3 / 3

Distinctiveness Conflict Risk

Scoped narrowly to creating PRs against the docker/docs repo with distinct triggers, making it unlikely to fire for unrelated skills.

3 / 3

Total

12

/

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

relative_links

Relative link issues: 1 missing

Warning

Total

15

/

16

Passed

Repository
docker/docs
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.