AB config-review-flow
Review and finalize configuration topics through a structured item-by-item confirmation flow. Use when the user wants a documented configuration review flow, wants to逐条核对配置 or 逐项确认配置, or needs a process that inventories all in-scope settings first, records decisions in a workspace `configuring/` file, and requires a final explicit pre-apply confirmation before any real configuration change. Do not use for single-setting Q&A or direct config editing without a review pass.
As a process B 70/100 · Nearly there — weak spots: result and completion
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: 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 70/100
- 0Result and completion. Does not say what the result is
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 70Inputs and preconditions. Inputs and preconditions are listed
- 70Failures and branches. 13 branches
- 85Steps. 89 steps, 1 vague phrases
- 100When it triggers. States when to use and when not to
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2321 tokens
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
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
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 475: enough signal without eating the budget
- +4Structure: 5 headings
- +3Step-by-step instructions: 89 items
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 88.