CtrlK
BlogDocsLog inGet started
Tessl Logo

new-branch-and-pr

Create a fresh branch, complete work, and open a pull request

58

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

72%

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-organized and appropriately lean for a simple instruction-only skill, but the workflow steps are directional rather than executable and lack explicit validation checkpoints, which cap actionability and workflow clarity.

Suggestions

Add concrete commands to the workflow steps (e.g., `git checkout -b <branch>`, `git push -u origin <branch>`, `gh pr create`) to make guidance copy-paste actionable.

Insert an explicit validation checkpoint such as "Run tests; only push when they pass" to add a feedback loop before the PR step.

Specify a branch-naming convention and a concise PR-body template so the output is concrete rather than generic.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's git competence with no padded explanation of concepts, fitting the lean-and-efficient anchor; it is not score 2 because there is no unnecessary explanation to tighten.

3 / 3

Actionability

Steps like "Create a descriptive branch from the latest main" and "Commit focused changes and push" give direction but omit concrete commands, branch-naming conventions, and PR-template details, matching the incomplete-guidance anchor; it is not score 3 because the guidance is not copy-paste executable and is not score 1 because the steps are concrete enough to act on.

2 / 3

Workflow Clarity

The five-step sequence is clearly ordered and mentions tests/verification, but validation checkpoints are implicit with no explicit validate-then-proceed feedback loop, fitting the steps-listed-but-checkpoints-implicit anchor rather than the explicit-validation clarity of score 3.

2 / 3

Progressive Disclosure

As a simple under-50-line skill with no external references and well-organized sections (Trigger, Workflow, Guardrails, Output), it meets the simple-skill exemption for a top score; it is not score 2 because the sections are clearly signaled and there is no content that should be split out.

3 / 3

Total

10

/

12

Passed

Description

60%

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 and uses proper third-person voice with concrete actions, but it lacks an explicit "Use when..." trigger clause and natural term variations like "PR", leaving the "when" dimension implied and limiting completeness and trigger coverage.

Suggestions

Add an explicit "Use when..." clause naming when to invoke this skill (e.g., "Use when starting work that should ship via a branch and pull request") to raise completeness to 3.

Include common trigger-term variations such as "PR", "feature branch", or "commit and push" so users naturally say the skill's keywords.

Tighten "complete work" into a more specific concrete action to fully earn the specificity anchor.

DimensionReasoningScore

Specificity

"Create a fresh branch, complete work, and open a pull request" lists multiple concrete actions (create branch, open PR), matching the multiple-specific-actions anchor; it is not score 2 because the actions are concrete rather than merely naming a domain, though the middle phrase "complete work" is comparatively generic.

3 / 3

Completeness

The description answers "what" (branch, work, PR) but provides no explicit "Use when..." trigger, so per the guidelines completeness is capped at 2 with "when" only implied.

2 / 3

Trigger Term Quality

It includes natural terms like "branch" and "pull request" but omits common variations such as "PR" or "feature branch", fitting the some-relevant-keywords-but-missing-variations anchor rather than the broad coverage of score 3.

2 / 3

Distinctiveness Conflict Risk

The branch-and-PR niche is specific, but without explicit trigger terms the description could overlap with generic git/version-control skills, matching the somewhat-specific-but-could-overlap anchor rather than the distinct-trigger clarity of score 3.

2 / 3

Total

9

/

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
cursor/plugins
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.