CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

new-branch-and-pr

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

Quality

75%

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 ./cursor-team-kit/skills/new-branch-and-pr/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%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.

The body is an efficient, well-structured overview whose steps are clearly sequenced, but it stops short of executable guidance — no commands, branch-naming conventions, or explicit validation checkpoints — leaving the workflow to be filled in by inference.

Suggestions

Add the concrete commands for each step (e.g. 'git switch -c <descriptive-name> origin/main', 'gh pr create --fill') so the workflow is copy-paste executable.

Make validation an explicit step in the workflow (e.g. 'Run tests; only commit when they pass') instead of an implicit part of 'complete implementation and tests'.

Specify what a 'descriptive branch' name and a 'concise PR summary' should look like with one short example each.

DimensionReasoningScore

Conciseness

The ~25-line body is lean with no padding and no explanation of concepts Claude already knows; every line (Trigger, Workflow, Guardrails, Output) earns its place.

5 / 5

Actionability

The workflow gives a concrete sequence ('Create a descriptive branch from the latest main', 'Commit focused changes and push') but includes no executable commands (git switch -c, gh pr create), branch-naming convention, or PR summary template, so key execution details are missing.

3 / 5

Workflow Clarity

Five steps are clearly ordered with a precondition check, but validation is only implicit ('complete implementation and tests' as a step, verification notes relegated to Guardrails) rather than an explicit checkpoint in the sequence.

3 / 5

Progressive Disclosure

A simple skill under 50 lines with well-organized sections (Trigger, Workflow, Guardrails, Output) and no need for external references, satisfying the simple-skill exception.

5 / 5

Total

16

/

20

Passed

Description

66%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.

The description states its purpose concisely in third person with recognizable trigger terms, but it omits any 'Use when...' guidance and leans on the vague 'complete work', limiting completeness and distinctiveness.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to start work on a new branch, ship changes via a PR, or open a pull request.'

Replace the generic 'complete work' with the concrete intermediate actions (commit, push, run tests) to raise specificity.

Include common synonyms such as 'PR' and 'feature branch' so natural user phrasings match.

DimensionReasoningScore

Specificity

Names concrete actions ('Create a fresh branch', 'open a pull request') alongside the generic 'complete work', matching the several-specific-actions-with-minor-gaps anchor rather than the 1-2-actions anchor or the comprehensive-coverage anchor.

4 / 5

Completeness

The 'what' is clear but there is no 'Use when...' clause or equivalent trigger guidance, which the guidelines cap at 3; it is not a 4 because the 'when' is entirely absent rather than merely imprecise.

3 / 5

Trigger Term Quality

'branch' and 'pull request' are natural terms users would say, but common variations like 'PR', 'feature branch', and 'commit' are missing, fitting the good-coverage-with-a-few-missing anchor.

4 / 5

Distinctiveness Conflict Risk

The git branch + pull request niche is mostly distinct with clear triggers, but the broad phrase 'complete work' and overlap with general git/commit workflow skills keep it from the minimal-conflict anchor.

4 / 5

Total

15

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

cursor/plugins

Path

cursor-team-kit/skills/new-branch-and-pr/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.