AB engagelab-otp
Call EngageLab OTP REST APIs to send one-time passwords (OTP), verify codes, send custom messages, and manage OTP templates across SMS, WhatsApp, Email, and Voice channels. Use this skill whenever the user wants to send an OTP or verification code via EngageLab, verify an OTP code, send custom messages through the OTP platform, manage OTP templates, configure callback webhooks, or integrate via SMPP. Also trigger when the user mentions "engagelab otp", "otp api", "send otp", "verify otp", "one-time password", "verification code", "engagelab verification", "otp template", "multi-channel otp", "whatsapp otp", "sms otp", "voice otp", "email otp", or asks to integrate with the EngageLab OTP platform. This skill covers OTP generation, delivery, verification, custom messaging, template management, callback configuration, and SMPP integration — use it even if the user only needs one of these capabilities.
As a process B 68/100 · Nearly there — weak spots: inputs and preconditions, running it twice, progress reporting
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: 8. 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 68/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 35 mutating operations with no state check
- 60Tools and files. Uses tools (bash, web, python) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 100Steps. 29 steps
- 100Failures and branches. 2 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2983 tokens
- 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)
- +3Description length 911: 120–800 characters recommended
- +1No license
- +2Single-language instructions
- +5Description quotes 13 example trigger phrases
- +4Structure: 34 headings
- +3Step-by-step instructions: 29 items
- +3Output format is stated explicitly
- +4Has examples (12 code blocks)
- +4Reference files are cited in the instructions (4 of 4)
- +3All 2 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 96.