AB var-protocol
Enforce Versioning, Archiving, and Rollback discipline for long-lived assets and multi-step delivery work. Use when editing codebases, websites, documents, decks, brand assets, prompts, configs, or any project artifact that needs safe iteration, backup-first handling, semantic version naming, changelogs, rollback anchors, or non-destructive updates. Trigger on requests about refactoring, major revisions, migration, redesign, rework, release packaging, version-control hygiene, or safe multi-agent collaboration. 中文简介：用于长期资产与多阶段交付的安全协作协议，核心是版本清晰、备份优先、遇错先回退，避免 destructive overwrite 导致资产丢失。
As a process B 67/100 · Nearly there — weak spots: result and completion, inputs and preconditions, running it twice
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: 3. 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 67/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
- 30Running it twice. 5 mutating operations with no state check
- 70When it triggers. States when to use, but not when not to
- 100Tools and files. No external tools needed
- 100Steps. 44 steps
- 100Failures and branches. 2 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 990 tokens
- low 10 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)
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 592: enough signal without eating the budget
- +4Structure: 11 headings
- +3Step-by-step instructions: 44 items
- +4Reference files are cited in the instructions (1 of 1)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.