AB working-tree-governor
Govern dirty git working trees by classifying runtime noise vs real source changes, defaulting to selective staging, verifying staged scope, and asking the operator when scope is ambiguous.
As a process B 75/100 · Nearly there — weak spots: inputs and preconditions, running it twice
AnalyzerSoftware developmentInfrastructuretype and topics are labelled automatically from the skill text
How to improve
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: 2. 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 75/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 30 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 60Result and completion. Output format stated, no completion criterion
- 100Tools and files. No external tools needed
- 100Steps. 100 steps
- 100Failures and branches. 5 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1916 tokens
- 100Progress reporting. Reports progress
- low 11 top-level sections: this looks like several domains in one skill
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)
- +2Single-language instructions
- +3Description length 189: enough signal without eating the budget
- +4Structure: 38 headings
- +3Step-by-step instructions: 100 items
- +3Output format is stated explicitly
- +4Has examples (5 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 88.
External checks
ClawHub: clean
This is an instruction-only git workflow skill that helps agents selectively stage and commit changes while avoiding logs, caches, and runtime noise.
LLM: benign (high) · VirusTotal: · 29 May 2026