SKILLEMALL.ai
GitHub ↗ RU Sign in

CF finishing-a-development-branch

The terminal step of /feature and /sprint. Routed to once commit-gate has cleared, to decide the branch's fate — merge via PR, open a PR, or discard. Direct merge to the default branch is forbidden; every change lands through a PR. Under /sprint the skill auto-selects "open PR" and surfaces the merge decision to the user.

arbiterForge/codeArbiter Agent Skills author: arbiterForge AGPL-3.0 1 file body ≈ 2 573 tokens Open the sourcegithub.com↗ analyzed 26 h ago

The terminal step of /feature and /sprint.

As a process F 53/100 · Will not run — References files that are not bundled: ../../includes/artifacts.md, ../../includes/verification-boundary.md, ../../skills/ca-pr/SKILL.md

ProcedureOperations and projectstype 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
C
82/100
safety, quality, tests
Safety 60%
100
Quality 40%
56
Run on models
none yet
Process rating
F
53/100
Will not run
References files that are not bundled: ../../includes/artifacts.md, ../../includes/verification-boundary.md, ../../skills/ca-pr/SKILL.md
Tools and files w 18
0
When it triggers w 12
20
Running it twice w 4
30
the three weakest of ten parameters · all ten
This is a copy of a skill from another catalog; the rating counts the canonical one: finishing-a-development-branch (arbiterForge/codeArbiter)

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
  2. The text references files that are not there: add them or drop the references.
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

  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • warning missing-ref reference to a missing file: ../../includes/artifacts.md
  • warning missing-ref reference to a missing file: ../../includes/verification-boundary.md
  • warning missing-ref reference to a missing file: ../../skills/ca-pr/SKILL.md

Process rating: all ten parameters 53/100

Will not run. References files that are not bundled: ../../includes/artifacts.md, ../../includes/verification-boundary.md, ../../skills/ca-pr/SKILL.md
  • 0Tools and files. 3 referenced file(s) missing: ../../includes/artifacts.md, ../../includes/verification-boundary.md, ../../skills/ca-pr/SKILL.md
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 30 mutating operations with no state check
  • 40Result and completion. Does not say what the result is
  • 50Failures and branches. 0 branches, has a failure section
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 100Steps. 29 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2573 tokens
  • 100Progress reporting. Reports progress
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing

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
  • +4No input/output examples
  • +1No license
  • +2Single-language instructions
  • +3Description length 323: enough signal without eating the budget
  • +4Structure: 7 headings
  • +3Step-by-step instructions: 29 items

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