CtrlK
BlogDocsLog inGet started
Tessl Logo

create-pr

Create a pull request for the current branch. Handles uncommitted changes, generates a PR title matching the `[{modules}] {type}: {description}` format enforced by CI, and fills in the PR description template. Trigger: 'create pr', 'open pr', 'submit pr', 'make pr'.

80

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-5

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 that sequences a multi-step PR creation process with explicit validation gates and stop conditions, while staying lean and assuming Claude's competence. External references are appropriately one level deep with clear navigation.

DimensionReasoningScore

Conciseness

Lean and efficient throughout: it assumes Claude's knowledge of git/gh and adds only domain-specific guidance (veomni module mapping, review gate, pitfall caveats) with no generic-concept padding.

5 / 5

Actionability

Fully executable, copy-paste-ready commands at every step — git branch/status/diff/log, gh pr view/create/edit with --body-file, tail extraction, mkdir — covering both new-PR and existing-PR paths.

5 / 5

Workflow Clarity

Steps 1–4 are clearly sequenced with explicit validation gates (uncommitted-changes confirmation, make quality fail→stop, no-commits-ahead→stop, /veomni-review risky verdict→stop, review-again-before-update) and module/type tables functioning as checklists.

5 / 5

Progressive Disclosure

No bundle files exist; the body is well-organized into labeled sections and its external references (.github/PULL_REQUEST_TEMPLATE.md, check_pr_title.yml, /veomni-review) are one level deep and clearly signaled, with no nesting.

5 / 5

Total

20

/

20

Passed

Description

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

A concise, highly specific description that names concrete actions, provides multiple natural trigger phrases, and explicitly covers both what the skill does and when to invoke it. Third-person voice and distinct niche keep conflict risk low.

DimensionReasoningScore

Specificity

Lists four concrete actions — "Create a pull request", "Handles uncommitted changes", "generates a PR title matching the [{modules}] {type}: {description} format enforced by CI", and "fills in the PR description template" — giving comprehensive coverage of the skill's capabilities.

5 / 5

Completeness

Explicitly answers both "what" (the four PR-creation actions) and "when" (an explicit "Trigger:" clause with concrete phrases), matching the anchor for clearly answering both.

5 / 5

Trigger Term Quality

Includes four natural trigger phrases a user would actually say — "create pr", "open pr", "submit pr", "make pr" — covering synonyms comprehensively.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear PR-creation niche with distinct trigger phrases and minimal overlap risk; written in third-person voice ("Handles", "generates", "fills") with no first/second person.

5 / 5

Total

20

/

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
ByteDance-Seed/VeOmni
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.