CtrlK
BlogDocsLog inGet started
Tessl Logo

review-and-ship

Review the current branch for bugs, intent fit, and test coverage; run or write tests; commit focused work; open or update a PR.

64

Quality

76%

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/review-and-ship/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%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 a lean, well-structured overview with executable commands and a clear sequenced workflow including a re-run feedback loop. It scores top marks on conciseness and progressive disclosure, with only minor actionability and validation-gating gaps.

DimensionReasoningScore

Conciseness

The body is lean and efficient—short imperative workflow steps, a compact command block, and terse guardrails—assuming Claude's competence with no padded explanations, matching 'lean and efficient; every token earns its place'.

5 / 5

Actionability

Provides executable commands (git fetch/diff/status, gh pr checks) and concrete workflow steps, but several steps like 'Fix critical issues' and 'Commit selective files with a concise message' stay high-level, leaving minor gaps versus copy-paste-ready guidance.

4 / 5

Workflow Clarity

A clear six-step sequence with a feedback checkpoint ('Fix critical issues before finalizing and re-run affected tests') and a readiness check via gh pr checks, but commit/push gating could be more explicit, matching 'clear sequence with most checkpoints present'.

4 / 5

Progressive Disclosure

Under 50 lines with no need for external references and clean section organization (Trigger, Workflow, Suggested Checks, Guardrails, Output), which the rubric's simple-skill guidance scores at 5.

5 / 5

Total

18

/

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 is specific and action-oriented with good natural trigger terms and a clear distinct niche, but it lacks an explicit 'Use when' trigger clause, which caps its completeness. Adding a concise trigger phrase would lift the completeness and trigger-term dimensions.

Suggestions

Append a 'Use when...' clause, e.g. 'Use when finalizing a branch before shipping or when the user asks to review changes and open a PR.'

Add a few natural synonyms users might say, such as 'pull request' alongside 'PR' or 'ship', to broaden trigger-term coverage.

Optionally name the review dimensions more concretely (e.g. 'regressions, security') to push specificity toward comprehensive coverage.

DimensionReasoningScore

Specificity

Names the domain (branch review) and several concrete actions—"Review the current branch for bugs, intent fit, and test coverage", "run or write tests", "commit focused work", "open or update a PR"—with only minor coverage gaps, fitting the 'lists several specific actions' anchor rather than the fully comprehensive 5.

4 / 5

Completeness

The description gives a clear "what" but contains no explicit "Use when..." clause or equivalent trigger guidance, which the judging guidelines cap at 3.

3 / 5

Trigger Term Quality

Includes natural terms users would say ("bugs", "test coverage", "tests", "commit", "PR") but omits common synonyms/variations like "pull request" spelled out or "ship", so it sits at good-but-not-comprehensive coverage.

4 / 5

Distinctiveness Conflict Risk

It targets a fairly distinct niche (pre-ship branch review, commit, PR) with only minor overlap risk against general coding skills, matching 'mostly distinct; minor overlap risk'.

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.

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.