BC fix-ci
Fix the failed CI checks for the current session. Use when the user requests a CI fix via the Fix Checks button in the Changes toolbar.
The skill promises to fix failed CI checks via a button in the interface. Single file with 258 tokens of instructions, no scripts. Quality score 76, process score 54—middling. No critical errors flagged. Works across all major platforms from Claude to DeepSeek.
No broken links or syntax issues in the file. Grade B signals it's functional but unremarkable. For emergency CI fixes within a session, it likely parses error logs and suggests patches. Install if you frequently hit failing checks and want to automate the initial diagnostic pass.
Fix the failed CI checks for the current session.
As a process C 54/100 · Has gaps — weak spots: result and completion, inputs and preconditions, failures and branches
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 54/100
- 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. 1 mutating operations with no state check
- 70When it triggers. States when to use, but not when not to
- 85Steps. 4 steps, 1 vague phrases
- 100Tools and files. No external tools needed
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 258 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)
- +4Structure: 2 headings, hard to scan
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 135: enough signal without eating the budget
- +3Step-by-step instructions: 4 items
Quality base 70; lint remarks subtract, signals add up to 100. Result: 76.