CF merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
Promises to prepare and merge a PR batch with author credits and candidate validation. Actually an analyzer for pasted PR lists that runs inside the chat. One file, no scripts, models untested. Mid-range scores: quality 71, process 32, safety 95. One medium-severity finding left undescribed. Broken references indicate missing files in the package.
Diagnostics work, but real merges still need full standard checks and approvals outside this skill. Install if you need quick PR-list parsing before the main review workflow; don't rely on it solo for production.
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission.
As a process F 32/100 · No process to follow — References files that are not bundled: scripts/quality/check-skill-contract.mjs
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The skill asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.
Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.
How to improve
- The text references files that are not there: add them or drop the references.
- 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 · 1
✓ No critical or high findings
Medium and low: 1
-
medium Broad scope
meta-broad-allowed-toolsSKILL.md:1Broad tool permissions pre-approved: Bashallowed-tools: Bash Read Edit Write Grep Glob AskUserQuestion
Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: scripts/quality/check-skill-contract.mjs
Process rating: all ten parameters 32/100
- 0Tools and files. 1 referenced file(s) missing: scripts/quality/check-skill-contract.mjs
- 0Steps. Prose only: no discrete steps
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 5 mutating operations with no state check
- 40Result and completion. Does not say what the result is
- 50When it triggers. No condition that starts the skill
- 50Failures and branches. 0 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1334 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)
- +3No numbered steps or checklist
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 249: enough signal without eating the budget
- +4Structure: 6 headings
Quality base 70; lint remarks subtract, signals add up to 100. Result: 71.