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.

85

1.87x
Quality

83%

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

85%

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

A well-structured, highly actionable shipping workflow with clear sequencing and validation feedback loops. The only weakness is minor verbosity from repeated preconditions and motivational reinforcement lines.

Suggestions

Drop the duplicated 'Assumes code is already committed and pushed' line from the body since it already appears in the description.

Trim the persuasive reinforcement ('You are an LLM. You have no time constraints. Fix everything.') to a concise directive like 'Fix every finding; defer nothing.'

Consolidate the repeated fix/commit/push instruction across Phases 2, 3, and 6 into a single referenced step to reduce token repetition.

DimensionReasoningScore

Conciseness

The body is mostly efficient and command-driven, but repeats the precondition ('Assumes code is already committed and pushed') already in the description and includes emphatic reinforcement lines ('You are an LLM. You have no time constraints. Fix everything.') that could be tightened, fitting the level-2 anchor.

2 / 3

Actionability

It provides concrete, copy-paste-ready commands ('gh pr create --base dev ...', 'gh run watch <id>', 'git branch --show-current') and names specific MCP tools, matching the fully-executable level-3 anchor.

3 / 3

Workflow Clarity

The seven phases are clearly sequenced with explicit validation checkpoints and feedback loops (CI fail → fix → retry; re-run Phase 2 and Phase 3 after fixes; re-read findings to confirm), matching the level-3 anchor.

3 / 3

Progressive Disclosure

No bundle files are present and none are needed; the single SKILL.md is well-organized into clearly labeled phases, so per the simple-skills note a single self-contained, well-sectioned file scores 3.

3 / 3

Total

11

/

12

Passed

Description

82%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, concise description that names concrete actions and uses natural trigger terms with a clear niche. Its main gap is the absence of an explicit 'Use when...' trigger clause, which caps completeness.

Suggestions

Add an explicit 'Use when...' clause naming triggers (e.g., 'Use when the user asks to ship, finalize, or land the current branch after code is committed and pushed').

Reinforce the trigger with common phrasings users might say like 'land this branch' or 'get this branch ready to merge'.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — 'CI, SonarCloud, code review, security review, fix all issues, merge' — matching the level-3 anchor of several specific actions rather than the single-action level-2 anchor.

3 / 3

Completeness

It clearly states what the skill does, but provides no 'Use when...' trigger clause — only the precondition 'Assumes code is already committed and pushed' — so per the judging guidelines completeness is capped at 2.

2 / 3

Trigger Term Quality

It uses natural terms a user would say — 'ship', 'CI', 'code review', 'security review' — giving good coverage; it is not merely technical jargon (level 1) nor missing common variations (level 2).

3 / 3

Distinctiveness Conflict Risk

The narrow 'ship current branch' niche with the named review gates is clearly distinguishable and unlikely to fire for unrelated skills, matching the level-3 'clear niche' anchor.

3 / 3

Total

11

/

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.

Validation16 / 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.