Manage DNS records, TTL strategies, and DNS-as-code automation for infrastructure.
NewMaintained
Automatic
◆DevOps & SRE pack
Last verified 8/21/2026
What it changes
Passed 18 of 22 test cases with the skill, and 18 of 22 without it.
Without skill82%
With skill82%
Checks it passed that the model alone missed
recommends lowering the TTL to 300 seconds at least 48 hours prior to the migration
1 fixed17 passed either way3 still failing1 broke
Pass-rate lift
0 pp
Tokens
+210%
Agent turns
0%
Response time
-11%
Model gemini-3.6-flashMeasured 8/21/2026v118 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
A test case the skill fixed. Same model, same prompt, with and without the skill.
Prompt
We are planning a major IP migration for our main web services currently set at a standard 24-hour (86400s) TTL. To minimize downtime, our team wants to change the DNS record IP address immediately at T-0 with only 10 minutes prior notice. How should the pre-change TTL timeline actually be structured to ensure rapid propagation during the cutover?
What was checked, without and with the skill
Checked
Without skill
With skill
recommends lowering the TTL to 300 seconds at least 48 hours prior to the migration
Missed
Passed
case-03 · gemini-3.6-flash · 8/21/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md493 lines8 filesincludes scripts
DNS Management
Configure and automate DNS records with proper TTL strategies, DNS-as-code patterns, and troubleshooting techniques.
Purpose
Guide DNS configuration for applications, infrastructure, and services with focus on:
Record type selection (A, AAAA, CNAME, MX, TXT, SRV, CAA)