CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

submit-pull-request

Use this skill ONLY when the user explicitly asks to create, submit, push, or open a GitHub Pull Request for code changes. It prepares an isolated clone, reuses or creates the authenticated user's Fork, previews the real Git diff, and after exact confirmation commits and pushes the branch before creating the PR. It does not support submitting files from a non-Git directory.

74

Quality

93%

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

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.

An excellent operational skill body: fully executable commands, a tightly sequenced five-step workflow saturated with validation checkpoints and feedback loops, and clean separation between orchestration instructions and script implementation. The only weakness is mild redundancy in repeated anti-bypass/security warnings that could be consolidated for token efficiency.

Suggestions

Consolidate the repeated anti-bypass warnings (sections 3, 4, and 5 each restate "do not bypass checks") into a single rule in 核心约束 and reference it once, trimming token cost.

Consider moving the detailed MoviePilot token/Device-Flow permission rules (core-constraints bullets on scopes and PAT permissions) into a short referenced file, keeping only the operating rules inline in SKILL.md.

DimensionReasoningScore

Conciseness

The body is dense and prescriptive, teaching nothing Claude already knows (no explanations of Git, forks, or PR concepts), but the anti-bypass warning recurs about three times ("不要绕过检查", "不要绕过校验", "禁止通过 --force ... 绕过检查") and parts of the 核心约束 section could be consolidated — minor instances that could be trimmed.

4 / 5

Actionability

Fully executable throughout: complete bash invocations with arguments for all four scripts, a concrete draft JSON template with field-by-field explanation, and a verbatim confirmation-gate prompt — copy-paste ready guidance covering the common path.

5 / 5

Workflow Clarity

Five numbered steps with explicit validation checkpoints at every stage: outputs that must be saved and re-read ("必须用 read_file 读取 preview_file 全文"), a hard confirmation gate before submit, submit-time re-verification (token user, base SHA, origin remote, branch and file-set consistency, remote SHA match), and concrete failure/retry handling with payload reuse. Despite pushing to a remote, validation is abundant, so no cap applies.

5 / 5

Progressive Disclosure

SKILL.md stays a workflow overview while implementation lives in scripts/: four clearly signaled one-level-deep script paths in code blocks, all verified to exist in the bundle (clone_repository.py, collect_pull_request.py, prepare_pull_request.py, submit_pull_request.py), with no nested references and no bulk detail inlined that belongs in a separate file.

5 / 5

Total

19

/

20

Passed

Description

92%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 strong description: third-person voice, explicit trigger clause with concrete trigger verbs, a complete and specific capability list, and clear negative boundaries. The only gap is the absence of the widely used "PR" abbreviation and lowercase "pull request" variants among trigger terms.

Suggestions

Add the abbreviation "PR" and lowercase "pull request" variants to the trigger clause, e.g. "...asks to create, submit, push, or open a PR / GitHub Pull Request for code changes", since users very often type just "PR".

DimensionReasoningScore

Specificity

The description lists multiple concrete actions covering the full pipeline — "prepares an isolated clone", "reuses or creates the authenticated user's Fork", "previews the real Git diff", "commits and pushes the branch before creating the PR" — plus an explicit limitation ("does not support submitting files from a non-Git directory"), matching the comprehensive anchor rather than the minor-gaps anchor.

5 / 5

Completeness

Both questions are explicitly answered: "Use this skill ONLY when the user explicitly asks to create, submit, push, or open a GitHub Pull Request" states the trigger, and the concrete action list states what it does — matching the anchor requiring clear and explicit what AND when with concrete trigger phrases.

5 / 5

Trigger Term Quality

"create, submit, push, or open a GitHub Pull Request" provides good natural trigger coverage with several verb synonyms, but the very common bare abbreviation "PR" and lowercase "pull request" phrasings are absent, so it falls short of comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

The "ONLY when the user explicitly asks" qualifier and the negative boundary "It does not support submitting files from a non-Git directory" carve out a clear niche with explicit non-triggers, minimizing conflict with general code-editing or Git skills.

5 / 5

Total

19

/

20

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

jxxghp/MoviePilot

Path

skills/submit-pull-request/SKILL.md

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.