BC auto-commit
Triggers on any task that modifies code. Provides instructions to surgically stage and commit only the modified code files to save progress.
As a process C 62/100 · Has gaps — weak spots: result and completion, inputs and preconditions, progress reporting
ReferenceSoftware developmentInfrastructuretype and topics are labelled automatically from the skill text
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
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: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 62/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
- 60Tools and files. Uses tools (bash, git) that frontmatter does not declare
- 65Failures and branches. 3 branches
- 100Steps. 5 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 269 tokens
- 100Running it twice. Mutating operations check current state
- low The response is described with custom markup (3 tags): a typed call is more reliable
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
- -41 reference files, but SKILL.md never points to them: the model will not open them
- +1No license
- +2Single-language instructions
- +3Description length 140: enough signal without eating the budget
- +4Structure: 3 headings
- +3Step-by-step instructions: 5 items
Quality base 70; lint remarks subtract, signals add up to 100. Result: 64.
External checks
ClawHub: clean
This skill openly tells the agent to make local Git commits after code changes, which matches its purpose but needs careful use.
LLM: benign (medium) · VirusTotal: · 29 May 2026