new-branch-and-pr

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

Quality

61%

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

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 a tight, well-structured process skill that respects token budget and organizes content cleanly. Its main weakness is that the workflow steps stay at the directive level without concrete commands or explicit inline validation checkpoints.

Suggestions

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

Insert an explicit validation checkpoint in the sequence, e.g. 'Run tests; only commit when they pass' before the commit step.

Make the verification expectation inline in the workflow rather than only in Guardrails so the feedback loop is visible in sequence.

Dimension	Reasoning	Score
Conciseness	The body is lean with no padding or explanation of concepts Claude already knows; every line (Trigger, Workflow, Guardrails, Output) earns its place.	3 / 3
Actionability	Steps are actionable directives ('Create a descriptive branch from the latest main', 'Commit focused changes and push') but lack concrete commands such as git/gh invocations, leaving key details implicit.	2 / 3
Workflow Clarity	The five steps are clearly sequenced, but validation checkpoints are only implicit (tests in step 3, verification notes in Guardrails) rather than explicit inline checkpoints in the workflow.	2 / 3
Progressive Disclosure	At under 50 lines with no bundle files and no need for external references, the well-organized Trigger/Workflow/Guardrails/Output sections meet the bar for a simple skill.	3 / 3
	Total	10 / 12 Passed

Description

50%

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 the core actions clearly and uses natural terms, but it omits any explicit 'Use when...' trigger guidance and leans on a vague middle clause. It reads as a competent but incomplete description that would benefit from explicit triggers and tighter action wording.

Suggestions

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

Replace the generic 'complete work' with a more concrete action or drop it so every listed verb is specific.

Include common trigger variations such as 'PR', 'feature branch', or 'submit changes for review' to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	Lists concrete actions ('Create a fresh branch', 'open a pull request') but the middle clause 'complete work' is generic filler, so it names the domain and some actions without being comprehensive.	2 / 3
Completeness	It clearly states what the skill does but provides no 'Use when...' clause or equivalent explicit trigger guidance, so the 'when' is missing rather than explicit.	2 / 3
Trigger Term Quality	'branch' and 'pull request' are natural terms users would say, but common variations like 'PR', 'feature branch', or 'fork' are absent, so coverage is partial.	2 / 3
Distinctiveness Conflict Risk	The branch-and-PR niche is somewhat specific but could still overlap with broader git/commit skills, and without distinct trigger phrasing the conflict risk is not fully resolved.	2 / 3
	Total	8 / 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 — 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: fe77e77

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.