new-branch-and-pr

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

Quality

31%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./cursor-team-kit/skills/new-branch-and-pr/SKILL.md

Quality

Content

29%

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

This skill reads more like a high-level checklist or process outline than an actionable skill. It lacks any concrete git or GitHub CLI commands, specific examples of branch naming conventions, commit message formats, or PR body templates. While the structure is clean and concise, the content doesn't give Claude enough executable guidance to reliably perform the task.

Suggestions

Add concrete, executable commands for each workflow step (e.g., `git fetch origin && git checkout -b feat/description origin/main`, `gh pr create --title '...' --body '...'`)

Include a specific example of a branch name, commit message, and PR body template so Claude knows the expected format

Add a validation checkpoint after pushing (e.g., verify the branch exists on remote, verify CI passes before creating PR)

Include error handling guidance for common issues like dirty working tree, merge conflicts, or push failures

Dimension	Reasoning	Score
Conciseness	The content is relatively brief and doesn't over-explain concepts Claude knows, but it's also quite thin—mostly generic descriptions without much substance. The guardrails and output sections are lean but the workflow steps are vague filler rather than earning their tokens.	2 / 3
Actionability	No concrete commands, code, or executable examples are provided. Steps like 'Create a descriptive branch from the latest main' and 'Complete implementation and tests' are vague directions rather than actionable instructions—no git commands, no gh CLI examples, no PR template.	1 / 3
Workflow Clarity	While steps are listed in sequence, they lack any concrete commands (e.g., `git checkout -b`, `gh pr create`), have no validation checkpoints, and 'Complete implementation and tests' is an entire unbounded task collapsed into one bullet. There's no error handling or feedback loop for common issues like merge conflicts or failed pushes.	1 / 3
Progressive Disclosure	For a simple, short skill with no bundle files, the content is appropriately organized into clear sections (Trigger, Workflow, Guardrails, Output) without unnecessary nesting or references. The structure is clean and navigable.	3 / 3
	Total	7 / 12 Passed

Description

32%

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 captures a git workflow at a high level but suffers from the vague phrase 'complete work' and lacks any explicit trigger guidance ('Use when...'). It would benefit from specifying what kind of work it handles and including natural trigger terms users would say when requesting this workflow.

Suggestions

Add a 'Use when...' clause with trigger terms like 'make a PR', 'submit changes', 'create a pull request', 'new feature branch', 'branch and PR workflow'.

Replace 'complete work' with specific actions like 'implement code changes', 'make edits', or 'apply fixes' to clarify what the skill actually does between branching and PR creation.

Include common keyword variations such as 'PR', 'merge request', 'git workflow', 'feature branch' to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	Names three specific actions (create branch, complete work, open PR), but 'complete work' is vague and the description lacks detail about what kind of work or how it's completed.	2 / 3
Completeness	Describes what it does (create branch, do work, open PR) but has no 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric, missing 'Use when' caps completeness at 2, and the 'what' is also weak due to vagueness of 'complete work'.	1 / 3
Trigger Term Quality	Includes natural terms like 'branch', 'pull request' that users would say, but misses common variations like 'PR', 'merge request', 'git', or 'feature branch'. 'Complete work' is too generic to serve as a trigger.	2 / 3
Distinctiveness Conflict Risk	The combination of branch creation + PR opening is somewhat distinctive as a workflow skill, but 'complete work' is so broad it could overlap with many development-related skills. It's not clearly distinguished from general git skills or code editing skills.	2 / 3
	Total	7 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: cursor/plugins
Commit: cfd81b3

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.