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%

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

The body is well-structured, executable, and concise, with a clear multi-step workflow and explicit validation/stop conditions at each risky point. No bundle files are required and the content is appropriately self-contained. No changes needed.

DimensionReasoningScore

Conciseness

Lean and purposeful: every section adds specifics Claude would not already know (the module-mapping table, the exact title regex/format, the draft-file convention) with no padding or explanation of basic concepts.

3 / 3

Actionability

Provides fully executable bash/gh commands with concrete flags (--body-file, --base), a copy-paste-ready draft-file template, and explicit filename conventions for both new and existing PRs.

3 / 3

Workflow Clarity

Four clearly sequenced steps with explicit validation checkpoints: stop on main branch, confirm uncommitted changes, stop if no commits ahead, stop on make quality failure, and the create-vs-update branch with file rename.

3 / 3

Progressive Disclosure

Single self-contained SKILL.md with well-organized sections and no external bundle files needed; references to repo files (template, CI workflow) are real paths signaled one level deep.

3 / 3

Total

12

/

12

Passed

Description

100%

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 is concise, specific, and answers both what the skill does and when to use it with explicit trigger phrases. It is written in clear, third-person voice and avoids fluff. No changes needed.

DimensionReasoningScore

Specificity

Lists multiple concrete actions: handling uncommitted changes, generating a CI-enforced title format, filling the PR description template, and pushing/creating the PR.

3 / 3

Completeness

Explicitly states what the skill does (creates PRs, handles uncommitted changes, generates title, fills template) and when to use it via an explicit 'Trigger:' clause.

3 / 3

Trigger Term Quality

Includes natural trigger phrases users would say — 'create pr', 'open pr', 'submit pr', 'make pr' — covering common variations.

3 / 3

Distinctiveness Conflict Risk

Targets a clear, narrow niche (PR creation for a specific repo's CI title format) with distinct triggers unlikely to collide with other skills.

3 / 3

Total

12

/

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.

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.