network-dns-tls-edge-management
Skill8 starsChanged 5 months agoMITView on GitHub
Plan and operate DNS, TLS certificates, ACME, Caddy/Ingress/reverse proxies, edge routing, TTL, cutovers, validation, and rollback. Use before changing a public hostname, certificate, load-balancer route, ingress, proxy, firewall exposure, or DNS provider record.
In this repository68 other files it gives its agents.
- animejsSkill
- sketch-animation-videoSkill
- sound-fx-for-videoSkill
- content_series_infographicSkill
- tech-article-seriesSkill
- ansible-playbookSkill
- gin-goSkill
- github-actionsSkill
- iac-hclSkill
- nodejs-nextjs-typescriptSkill
- postgresql-developmentSkill
- programming-paradigmsSkill
- python-shellSkill
- agent-team-harnessSkill
- ai-agent-collaboration-standardSkill
- ci-cd-workflow-specSkill
- config-as-code-specSkill
- execution-ownership-migrationSkill
- feature-lane-release-workflowSkill
- generation-upgrade-acceptanceSkill
- gitops-canonical-resource-deliverySkill
- harness-workflowSkill
- infrastructure-as-code-specSkill
- issue-pr-traceability-standardSkill
- multi-environment-delivery-and-releaseSkill
- project-development-standardSkill
- store-and-startup-homepage-specSkill
- zero-trust-overlay-deliverySkill
- it-infra-continuous-pngSkill
- image-svg-pptx-proSkill
- autoglm-websearchSkill
- blogwatcherSkill
- Browser AutomationSkill
- docxSkill
- find-skillsSkill
- image-cogSkill
- image-resizerSkill
- pdfSkill
- pptxSkill
- Self-Improving Agent (With Self-Reflection)Skill
- skill-security-checkSkill
- skill-vetterSkill
- video-translatorSkill
- wan-image-video-gen-editSkill
- xlsxSkill
- backup-disaster-recovery-and-data-migrationSkill
- capacity-cost-and-resource-lifecycleSkill
- github-actions-operational-dispatchSkill
- incident-response-and-change-managementSkill
- observability-slo-and-alertingSkill
- secrets-identity-and-access-governanceSkill
- service-catalog-and-runbook-standardSkill
- system-db-three-role-securitySkill
- unified-observability-architectureSkill
- vault-eso-tls-certificate-governanceSkill
- ai-tech-news-videoSkill
- ai-ti-wo-shuo-explainerSkill
- it-infra-evolution-videoSkill
- it-infra-evolution-video-v2Skill
- product-intro-videoSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 26
Keep the previous route and certificate material available through the observation window.
- Distinctive: line 28
Do not delete old records, IPs, certificates, or hosts as part of the cutover unless explicitly approved after verification.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Network, DNS, TLS, and Edge Management
DNS and certificate changes are traffic-routing changes. Validate authoritative state and reachability before deploying a proxy or requesting a certificate; retries cannot repair NXDOMAIN or a wrong target.
1. Change record
For each public endpoint, record owner, canonical hostname, aliases, authoritative DNS zone/provider, record type/value, TTL, ingress/load-balancer target, certificate issuer, renewal owner, health endpoint, and rollback target.
2. Preflight
- Resolve A/AAAA/CNAME from authoritative and public resolvers. Confirm the desired record exists, points to the intended target, and has no conflicting IPv6/alias path.
- Confirm firewall/security-group/load-balancer reachability for the challenge and serving ports. Verify the edge target serves the expected health endpoint and virtual host.
- For ACME, validate DNS and challenge reachability before triggering Caddy/Ingress certificate issuance. Treat NXDOMAIN, stale AAAA, or inaccessible challenge traffic as a DNS/network change, not an application retry problem.
- Inspect certificate SANs, issuer, expiry, chain, redirect behavior, and application-level HTTPS health after change.
3. Cutover and rollback
- State current target, desired target, TTL/propagation expectation, success signal, rollback target, and observation window.
- Make the edge/proxy configuration and target healthy before DNS cutover.
- Apply the smallest record/routing change, verify authoritative and public resolution, then validate TLS and user-facing health from independent locations.
- Keep the previous route and certificate material available through the observation window. Roll back on declared health criteria, not on operator preference.
Do not delete old records, IPs, certificates, or hosts as part of the cutover unless explicitly approved after verification. Keep DNS credentials in Vault-backed workload identity; never put provider API keys in repository variables or logs.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

