AB openprovider
OpenProvider domain registrar & DNS management. Triggers on: register domain, buy domain, renew domain, transfer domain, delete domain, restore domain, add DNS record, change DNS, create DNS zone, list DNS records, delete DNS zone, order SSL certificate, renew SSL, revoke SSL, change nameservers, nameserver group, TLD prices, TLD info, WHOIS, domain owner, registrant, customer handle, create contact, OpenProvider, Openprovider, domain available, check domain, domain search, domain suggestions, bulk domain check, auto-renew, auth code, EPP code, domain status, DNS propagation, MX record, SPF record, DKIM record, DMARC record, A record, CNAME record, TXT record, reseller, domain pricing, domain cost
As a process B 69/100 · Nearly there — weak spots: result and completion, inputs and preconditions, progress reporting
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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: 10. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 69/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 40Result and completion. Does not say what the result is
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 85Steps. 50 steps, 1 vague phrases
- 100When it triggers. States when to use and when not to
- 100Failures and branches. 2 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3392 tokens
- 100Running it twice. Mutating operations check current state
- 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
- +1No license
- +2Single-language instructions
- +3Description length 706: enough signal without eating the budget
- +4Structure: 23 headings
- +3Step-by-step instructions: 50 items
- +4Has examples (9 code blocks)
- +4Reference files are cited in the instructions (7 of 7)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 76.