SKILLEMALL.ai

AD rebase

Start a local Git rebase when the user explicitly requests replay of a named source ref, or of the current branch, onto a named target, including a rebase-then-push request, which carries exact-lease publication to the branch's own remote destination, or continue or abort an active rebase. Use only when local history replay will start or is active; do not use for merge-based branch updates, repository merge settings, pull-request or merge-request merging, or push-only requests.

Jamie-BitFlight/claude_skills Agent Skills author: Jamie-BitFlight MIT 7 files body ≈ 3 444 tokens Open the sourcegithub.com↗ analyzed 6 h ago

Start a local Git rebase when the user explicitly requests replay of a named source ref, or of the current branch, onto a named target, including a…

As a process D 38/100 · Unfinished process — weak spots: steps, result and completion, inputs and preconditions

ReferenceSoftware developmenttype and topics are labelled automatically from the skill text
JSON
Technical rating
A
96/100
safety, quality, tests
Safety 60%
100
Quality 40%
89
Run on models
none yet
Process rating
D
38/100
Unfinished process
Steps w 15
0
Result and completion w 14
0
Inputs and preconditions w 11
0
the three weakest of ten parameters · all ten

How to improve

    For the model run — optional
    • 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: 6. 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 38/100

    • 0Steps. Prose only: no discrete steps
    • 0Result and completion. Does not say what the result is
    • 0Inputs and preconditions. Does not say what the process needs to start
    • 0Failures and branches. Linear process with no failure handling
    • 0Progress reporting. Says nothing while it works
    • 30Running it twice. 9 mutating operations with no state check
    • 60Tools and files. Uses tools (web) that frontmatter does not declare
    • 100When it triggers. States when to use and when not to
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 3444 tokens
    • low No test case covers injection arriving through data

    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

    • +5Description has no quoted example phrases that should trigger the skill
    • +3No numbered steps or checklist
    • +3Output format is not stated: the model decides each time
    • +1No license
    • +2Single-language instructions
    • +4Description says when NOT to use the skill
    • +3Description length 482: enough signal without eating the budget
    • +4Structure: 3 headings
    • +4Has examples (1 code blocks)
    • +4Reference files are cited in the instructions (5 of 5)

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