BC merge
Merge changes from the topic branch to the merge base branch. Use when the user wants to merge their session's work back to the base branch.
Promises to merge changes from a topic branch back to the base branch without friction. Contains one instruction file at 529 tokens, no scripts. Grade B: quality 84%, process only 59%. No critical errors, linter passes.
Runs on all major platforms from Claude to OpenClaw. Handles routine merges fine, but the low process score suggests the instruction may stumble on complex conflicts. Install it if you don't need merge guarantees on the first attempt.
Merge changes from the topic branch to the merge base branch.
As a process C 59/100 · Has gaps — weak spots: result and completion, inputs and preconditions, running it twice
How to improve
- 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 59/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 11 mutating operations with no state check
- 55Failures and branches. 1 branches
- 60Tools and files. Uses tools (read) that frontmatter does not declare
- 100Steps. 6 steps
- 100When it triggers. States when to use and when not to
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 529 tokens
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
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 140: enough signal without eating the budget
- +4Structure: 7 headings
- +3Step-by-step instructions: 6 items
- +4Has examples (8 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.