AC dns-doctor
Use when a domain's email is landing in spam, or you see SPF PermError / "too many DNS lookups", DMARC stuck at p=none, a "550 5.7.515" or "550 5.7.1" rejection, DKIM failures, a DNS change that may not have propagated yet, a domain that might be blacklisted, or many domains to check at once. Scans, fixes and verifies a domain's DNS — email authentication (SPF, DMARC, DKIM), multi-region propagation, SPF include supply-chain audits, MX, DNS health and domain/SSL expiry — via the DNS Doctor public API, and returns copy-paste fix records generated by a validating engine — never a guessed record. Free per caller; past the limit an x402-capable agent can pay per call (USDC on Base), no account needed.
7.515" or "550 5.7.1" rejection, DKIM failures, a DNS change that may not have propagated yet, a domain that might be blacklisted, or many domains to check at…
As a process C 60/100 · Has gaps — weak spots: result and completion, inputs and preconditions, running it twice
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 · 2
✓ No critical or high findings
Medium and low: 2
-
low Exfiltration
net-credential-useSKILL.md:122Credential used in a network call (verify the destination is the intended service) (documentation of a security skill)curl -s -H "Authorization: Bearer $DNSDOCTOR_API_TOKEN" \
security skill -
low Exfiltration
net-credential-useSKILL.md:126Credential used in a network call (verify the destination is the intended service) (documentation of a security skill)curl -s -H "Authorization: Bearer $DNSDOCTOR_API_TOKEN" \
security skill
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 60/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 28 mutating operations with no state check
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 70Execution cost. Instruction body is 4453 tokens
- 100Steps. 18 steps
- 100Failures and branches. 2 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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
- +2Single-language instructions
- +5Description quotes 3 example trigger phrases
- +3Description length 706: enough signal without eating the budget
- +4Structure: 11 headings
- +3Step-by-step instructions: 18 items
- +4Has examples (5 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 90.