CtrlK
BlogDocsLog inGet started
Tessl Logo

pr

Create a GitHub pull request from current working changes. Handles all git states - uncommitted changes, no branch, unpushed commits, etc. Analyzes diffs and changesets to generate a PR with filled-in template. Opens the PR in the browser when done. Use when the user asks to create a PR, open a PR, submit changes, or push for review.

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

Low

Low-risk findings worth noting

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.

A high-quality, self-contained workflow skill: actionable commands, a clear sequenced decision tree with a changeset validation gate, and a copy-paste PR template. The genuine gaps are minor — no explicit verification that the push succeeded before creating the PR, no error-recovery loop, and light command repetition across steps.

Suggestions

Add an explicit checkpoint after `git push -u origin HEAD` (e.g., verify `git status` shows the branch is up to date with origin, or capture push failure and retry) before running `gh pr create`, since a failed silent push would create a PR from stale commits.

Consolidate the repeated `ls .changeset/*.md | grep -v README` and `git status --porcelain` invocations between Step 1, Step 3, and Step 5 by computing state once and reusing it, to trim the small redundancy.

Note the `gh pr create` failure path (e.g., auth errors, base branch missing) so the workflow has a light error-recovery feedback loop rather than a linear happy path.

DimensionReasoningScore

Conciseness

Lean and command-dense throughout — parallel git/gh commands, direct numbered steps, and a compact template — with no padding about what a PR or conventional commit is; it is not the score-2 "could be tightened" case because the few repeated commands (git status, changeset ls) serve contextual re-verification rather than redundancy.

3 / 3

Actionability

Provides fully executable bash at every step (git checkout -b, git add -A, git push -u origin HEAD, gh pr create heredoc, gh pr view --web) plus a copy-paste-ready PR body template, matching the executable-and-specific anchor rather than the pseudocode/incomplete score-2 anchor.

3 / 3

Workflow Clarity

Steps 1–7 are clearly sequenced with a per-state decision tree in Step 2 and an explicit validation gate in Step 3 ("Validate Changesets and Blog (before committing)") plus a remediation path (invoke the changeset skill); it clears the score-3 bar via sequencing and a checkpoint even though it lacks explicit push-verification and error-recovery loops, which is why it is not a comfortable 3.

3 / 3

Progressive Disclosure

No bundle files exist, so per the no-external-references-needed scoring note the single self-contained file scores 3 on the strength of its clear Overview + numbered-steps + PR Title/Body Template/Create Command organization; the only cross-reference (the separate "changeset" skill) is clearly signaled and 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.

A strong, exemplar-style description: it names concrete capabilities, gives an explicit Use-when trigger with natural phrasings, and stays in third person. Its only soft spot is a couple of broad trigger terms that could in principle overlap with generic commit/push intents, but the PR framing keeps it distinctive.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "Create a GitHub pull request from current working changes", "Analyzes diffs and changesets to generate a PR with filled-in template", "Opens the PR in the browser when done" — matching the multiple-specific-actions anchor rather than the partial score-2 anchor.

3 / 3

Completeness

Explicitly states what it does (create/fill/open the PR) and an explicit "Use when the user asks to create a PR, open a PR, submit changes, or push for review" trigger clause, so it is not capped at 2 for a missing trigger clause.

3 / 3

Trigger Term Quality

Covers natural user phrasings — "create a PR", "open a PR", "submit changes", "push for review" — with both "PR" and "pull request" variants present, matching the good-coverage anchor rather than the some-keywords-missing score-2 anchor.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear GitHub-PR-creation niche with distinct triggers and consistent third-person voice ("Creates", "Handles", "Analyzes", "Opens"), so it is unlikely to fire for unrelated skills; "submit changes"/"push for review" are slightly broad but framed by the PR context, keeping it above the score-2 overlap anchor.

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
reactive/data-client
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.