AB infini-api
Guide users through Infini's basic API integration and webhook integration with step-by-step explanations, sandbox-first setup, and directly runnable Node.js or Python examples. Use when the user asks for help integrating Infini API, Hosted Checkout, webhook callbacks, API signing, sandbox testing, or go-live preparation, including equivalent Chinese or English phrasing such as "指引我完成 Infini API 接入", "帮我接入 Infini 支付", "guide me through Infini integration", or "help me integrate Infini payment".
As a process B 69/100 · Nearly there — weak spots: result and completion, inputs and preconditions
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: 6. 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 69/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 70When it triggers. States when to use, but not when not to
- 85Steps. 69 steps, 1 vague phrases
- 100Tools and files. No external tools needed
- 100Failures and branches. 7 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2015 tokens
- 100Running it twice. Mutating operations check current state
- 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
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +5Description quotes 4 example trigger phrases
- +3Description length 499: enough signal without eating the budget
- +4Structure: 12 headings
- +3Step-by-step instructions: 69 items
- +4Has examples (2 code blocks)
- +4Reference files are cited in the instructions (3 of 3)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 93.