new-branch-and-pr

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

Quality

56%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

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

Quality

Content

61%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 content is exceptionally concise and well-structured for a simple skill, but its steps lack concrete executable commands and the workflow omits explicit validation checkpoints before pushing/requesting review. Adding specific git/gh commands and a test-run checkpoint would meaningfully raise actionability and workflow clarity.

Suggestions

Add concrete commands to each step, e.g. `git checkout -b <branch> origin/main`, `git push -u origin <branch>`, and `gh pr create --fill`.

Insert an explicit validation step before requesting review, such as running the test suite and confirming it passes.

Specify the PR summary structure (e.g. summary, test notes, risk) so the Output section is actionable rather than a label list.

Dimension	Reasoning	Score
Conciseness	The body is a lean ~20 lines of sectioned bullets with zero padding and no explanation of concepts Claude already knows, fitting the 'lean and efficient; every token earns its place' anchor.	5 / 5
Actionability	The steps ('Create a descriptive branch from the latest main', 'Commit focused changes and push') are high-level hints with no concrete commands (e.g. git checkout -b, git push -u, gh pr create), matching 'minimal concrete guidance; high-level hints but missing specific steps to execute'.	2 / 5
Workflow Clarity	A clear five-step sequence is present, but the workflow involves pushing and opening a PR with no explicit validation checkpoint (e.g. run tests before push, verify CI before requesting review), and the guarding guideline flags missing verification for ship operations, fitting 'steps listed but validation gaps'.	3 / 5
Progressive Disclosure	This is a short single-purpose skill under 50 lines with no external references needed and well-organized sections (Trigger, Workflow, Guardrails, Output), which per the simple-skill exception can score 5 on progressive disclosure.	5 / 5
	Total	15 / 20 Passed

Description

51%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 clearly conveys the skill's purpose (branch + PR workflow) and is reasonably distinct, but it lacks an explicit 'Use when...' trigger clause and uses fairly generic action verbs. Adding trigger phrasing and more concrete actions would lift it above the midpoint.

Suggestions

Append an explicit trigger clause, e.g. 'Use when starting work that should ship via a branch and pull request'.

Replace generic verbs with concrete actions: 'create a feature branch from latest main, commit focused changes, push, and open a PR with a summary and test notes'.

Add common synonyms like 'PR' and 'feature branch' to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain (branch/PR workflow) and three concrete actions (create branch, complete work, open PR), but each action is generic ('complete work', 'create a fresh branch') with no concrete coverage of how, matching the 'domain plus 1-2 concrete actions, not comprehensive' anchor.	3 / 5
Completeness	The 'what' is clear (create a branch, complete work, open a PR), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 3.	3 / 5
Trigger Term Quality	'branch' and 'pull request' are relevant natural keywords a user would say, but common variations like 'PR', 'feature branch', or 'fork' are missing, fitting 'some relevant keywords but missing common variations'.	3 / 5
Distinctiveness Conflict Risk	The branch-and-PR workflow is a reasonably distinct niche unlikely to trigger for unrelated skills, with only minor overlap risk against generic git skills, fitting 'mostly distinct; minor overlap risk'.	4 / 5
	Total	13 / 20 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 — 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
Commit: 51a96e0

Reviewed: 2 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.