CtrlK
BlogDocsLog inGet started
Tessl Logo

ship

Ship current branch — CI, SonarCloud, code review, security review, fix all issues, merge. Assumes code is already committed and pushed.

67

Quality

80%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/ship/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

92%

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

This is a high-quality skill with excellent actionability and workflow clarity. It provides specific commands, clear phase sequencing, robust feedback loops for error recovery, and appropriate safety constraints (no auto-merge, no AI attribution). The only minor weakness is that all content is inline, though for this length it remains manageable.

DimensionReasoningScore

Conciseness

The skill is lean and efficient. Every section serves a purpose, there's no explanation of what git, PRs, or CI are, and it assumes Claude knows how to use these tools. The instructions are direct and imperative.

3 / 3

Actionability

Provides specific, executable commands (gh pr create, gh run list, git commands) with exact flags and arguments. Tool invocations are named explicitly (e.g., skill="review", get_project_quality_gate_status with specific project key). Copy-paste ready throughout.

3 / 3

Workflow Clarity

Excellent multi-phase workflow with clear sequencing, explicit feedback loops (CI fails → fix → retry from step 1, SonarCloud issues → fix → re-run Phase 2), validation checkpoints at each phase, and clear escalation criteria (5+ files architectural change). Phase 6 explicitly re-runs CI and SonarCloud after fixes.

3 / 3

Progressive Disclosure

The content is well-structured with clear phase headers and logical organization, but it's entirely self-contained with no references to external files. For a skill of this length (~80 lines) and complexity (7 phases), this is acceptable but could benefit from separating detailed troubleshooting or edge cases into referenced files.

2 / 3

Total

11

/

12

Passed

Description

67%

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 concise and action-oriented, listing a clear pipeline of specific steps for shipping a branch. Its main weakness is the lack of an explicit 'Use when...' clause, which would help Claude know exactly when to select this skill. Adding common user trigger phrases would also improve discoverability.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user wants to ship, land, or merge their current branch, or asks to run the full CI/review/merge pipeline.'

Include common trigger term variations users might say: 'deploy', 'land', 'PR', 'pull request', 'push to main', 'get this merged'.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: CI, SonarCloud, code review, security review, fix all issues, merge. Also specifies a precondition (code already committed and pushed).

3 / 3

Completeness

Clearly answers 'what' (CI, SonarCloud, code review, security review, fix issues, merge) and states a precondition, but lacks an explicit 'Use when...' clause with trigger guidance. Per rubric guidelines, missing 'Use when' caps completeness at 2.

2 / 3

Trigger Term Quality

Includes some natural terms like 'merge', 'CI', 'code review', 'security review', and 'ship', but misses common variations users might say like 'deploy', 'PR', 'pull request', 'push to main', 'land branch', or 'get this merged'.

2 / 3

Distinctiveness Conflict Risk

Describes a very specific end-to-end shipping workflow (CI + SonarCloud + review + fix + merge) that is clearly distinct from individual code review, CI, or merge skills. The combination of steps creates a clear niche.

3 / 3

Total

10

/

12

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
PaloAltoNetworks/shifter
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.