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.

83

1.87x
Quality

81%

Does it follow best practices?

Impact

77%

1.87x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

92%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 highly actionable and excellently structured, with concrete commands, explicit validation feedback loops, and a clear multi-phase sequence; the only minor weakness is a few lines of motivational padding.

DimensionReasoningScore

Conciseness

Lean and command-driven with no concept explanations, but motivational lines like 'You are an LLM. You have no time constraints. Fix everything.' and repeated 'defer nothing' rhetoric are minor padding that could be trimmed, placing it at 4 rather than 5.

4 / 5

Actionability

Fully executable guidance throughout — concrete `gh` commands (`gh pr create`, `gh run watch`, `gh run view --log-failed`) and named MCP tools (`get_project_quality_gate_status`, `search_sonar_issues_in_projects`) cover the common cases copy-paste ready.

5 / 5

Workflow Clarity

Seven clearly sequenced phases with explicit validation checkpoints and feedback loops (CI failure → diagnose/fix/push → re-run; SonarCloud issues → fix → re-run CI), and the destructive merge is explicitly gated ('DO NOT MERGE').

5 / 5

Progressive Disclosure

A self-contained single-file skill with no bundle directories and well-organized Phase 1–7 section headers; per the simple-skills note, this earns a 5 with clear organization and no need for external references.

5 / 5

Total

19

/

20

Passed

Description

71%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-rich with solid natural trigger terms, but it omits any explicit 'Use when' guidance, which caps completeness at 3 and leaves the trigger situation implicit.

Suggestions

Add an explicit 'Use when...' clause stating when Claude should invoke this skill (e.g., 'Use when the user asks to ship, finalize, or merge a completed branch through CI and review').

Include common trigger synonyms such as 'PR', 'pull request', and 'deploy' alongside 'ship' to broaden natural-term coverage.

Reframe the leading verb in third person ('Ships the current branch...') to align with the rubric's preferred voice.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'CI, SonarCloud, code review, security review, fix all issues, merge' — giving comprehensive coverage of the shipping workflow, matching the score-5 anchor.

5 / 5

Completeness

Has a clear 'what' but no explicit 'Use when...' trigger clause; the 'Assumes code is already committed and pushed' line is a precondition, not a trigger, so per the rubric cap completeness at 3.

3 / 5

Trigger Term Quality

Good natural keywords ('ship', 'CI', 'code review', 'security review', 'merge') a user would say, but missing common synonyms/variations like 'PR', 'pull request', or 'deploy', so it sits at 4 rather than 5.

4 / 5

Distinctiveness Conflict Risk

The full-pipeline orchestrator niche (CI + SonarCloud + review + security + merge) is mostly distinct, with only minor overlap risk against the individual review/security-review skills it delegates to.

4 / 5

Total

16

/

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.

Validation — 16 / 16 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.