AB upi-go-live-checklist
Drive a zero-to-first-test-payment UPI onboarding workflow with explicit readiness checks: provider selection, sandbox setup, credentials, webhook validation, test matrix, go-live gates, and incident rollback planning. Use when preparing to launch UPI payments safely.
As a process B 74/100 · Nearly there — weak spots: when it triggers, running it twice
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: 8. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 2, column 14: description: Drive a zero-to-first-test-payment UPI onboarding workflow with ex… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
Process rating: all ten parameters 74/100
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 6 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 60Result and completion. Output format stated, no completion criterion
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Tools and files. No external tools needed
- 100Steps. 67 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1443 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)
- +1No license
- +2Single-language instructions
- +3Description length 268: enough signal without eating the budget
- +4Structure: 19 headings
- +3Step-by-step instructions: 67 items
- +3Output format is stated explicitly
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 77.
External checks
ClawHub: clean
This is a planning checklist for launching UPI payments and does not include code that moves money, installs software, or accesses systems by itself.
LLM: benign (high) · VirusTotal: · 29 May 2026