SKILLEMALL.ai
GitHub ↗ RU Sign in

BB split-and-ship

Execute an approved split plan, shipping each change group separately as its own branch and PR or as sequential commits on the current branch. Use when the user asks to "split and ship", "ship the split plan", "create separate PRs", or "split changes into branches".

tobihagemann/turbo Agent Skills author: tobihagemann MIT 1 file body ≈ 1 590 tokens Open the sourcegithub.com↗ analyzed 5 h ago

Execute an approved split plan, shipping each change group separately as its own branch and PR or as sequential commits on the current branch.

As a process B 70/100 · Nearly there — weak spots: result and completion, inputs and preconditions

GeneratorWriting and documentsCommercetype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
B
94/100
safety, quality, tests
Safety 60%
100
Quality 40%
85
Run on models
none yet
Process rating
B
70/100
Nearly there
Inputs and preconditions w 11
0
Result and completion w 14
40
Tools and files w 18
60
the three weakest of ten parameters · all ten

The same skill appears in 1 more place: turbo

How to improve

    For the model run — optional
    • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
    • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

    Guard findings · 0

    ✓ No critical or high findings

    Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 70/100

    • 0Inputs and preconditions. Does not say what the process needs to start
    • 40Result and completion. Does not say what the result is
    • 60Tools and files. Uses tools (git) that frontmatter does not declare
    • 70When it triggers. States when to use, but not when not to
    • 100Steps. 35 steps
    • 100Failures and branches. 2 branches, has a failure section
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 1590 tokens
    • 100Running it twice. Mutating operations check current state
    • 100Progress reporting. Reports progress
    • low The response is described with custom markup (3 tags): a typed call is more reliable

    Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

    Quality signals

    • +4Description does not say when NOT to use the skill (false activations)
    • +3Output format is not stated: the model decides each time
    • +4No input/output examples
    • +1No license
    • +2Single-language instructions
    • +5Description quotes 4 example trigger phrases
    • +3Description length 266: enough signal without eating the budget
    • +4Structure: 13 headings
    • +3Step-by-step instructions: 35 items

    Quality base 70; lint remarks subtract, signals add up to 100. Result: 85.