CtrlK
BlogDocsLog inGet started
Tessl Logo

submit-draft-pr

Optionally create a draft PR to the upstream repo from a local source directory. Used by coding agents when a local source path is available in the context file.

67

Quality

80%

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

Fix and improve this skill with Tessl

tessl review fix ./.github/agents-prototype/skills/submit-draft-pr/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%

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

The body is highly actionable with executable bash commands and a well-sequenced workflow including validation checkpoints. The main weakness is minor verbosity from a duplicated notice block and placeholder template content.

Suggestions

De-duplicate the IMPORTANT notice block by defining it once and referencing it from the PR-body template to save tokens.

Move the per-repo upstream table or the PR body template into a reference file if the body grows, keeping the core workflow in SKILL.md.

DimensionReasoningScore

Conciseness

The body is instruction-focused and assumes competence, but the IMPORTANT notice block is duplicated (standalone and again inside the full template example), and the constraint list plus placeholder-heavy template add length that could be tightened.

2 / 3

Actionability

Steps 1, 3, and 5 provide fully executable bash (gh auth status, gh pr list, gh repo fork, gh pr create) with real flags and clearly marked placeholders, making them copy-paste ready.

3 / 3

Workflow Clarity

Six numbered steps are clearly sequenced with explicit validation checkpoints — prerequisite verification, an existing-PR duplicate check, and skip-and-log error handling for an outward-facing operation.

3 / 3

Progressive Disclosure

No bundle files are present; the skill is a single self-contained SKILL.md with well-organized sections (When to invoke, Steps, Per-repo table, Constraints) and one-level navigation, which suits a single-purpose skill.

3 / 3

Total

11

/

12

Passed

Description

75%

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 cleanly answers both what the skill does and when to invoke it, with a distinct niche. It is somewhat held back by single-action specificity and trigger phrasing that uses internal agent jargon rather than natural user terms.

Suggestions

Broaden the action list to concrete capabilities, e.g. "Create a draft PR to the upstream repo, compose the PR body, and check for duplicate PRs from a local source directory."

Reframe the trigger in natural user-facing terms: "Use when submitting a draft pull request, opening a PR to upstream, or when a local source path is available in the context file."

DimensionReasoningScore

Specificity

"create a draft PR to the upstream repo from a local source directory" names a concrete action, target, and input, but describes a single action rather than listing multiple specific concrete actions.

2 / 3

Completeness

It states both what it does ("create a draft PR to the upstream repo from a local source directory") and when to use it ("when a local source path is available in the context file") with an explicit trigger clause.

3 / 3

Trigger Term Quality

"Used by coding agents when a local source path is available in the context file" includes a relevant trigger, but leans on internal jargon ("coding agents", "context file") and misses common natural variations like "draft PR", "submit PR", or "pull request".

2 / 3

Distinctiveness Conflict Risk

The narrow focus on opening a draft PR from a local source path tied to a context file gives it a clear niche with distinct triggers, making broad conflicts unlikely.

3 / 3

Total

10

/

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
openvinotoolkit/openvino
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.