- Home
- Skills
- DevOps & Cloud
- Network Change Risk Review
More screenshots
Works with the AI Agents you already use
Network Change Risk Review
Network Change Risk Review is a bounded ToolForge Labs workflow.
$1
Network Change Risk Review
Example session with this skill installed
Review this plan to migrate our public API from an F5 load balancer to an AWS ALC. I have the DNS TTL settings, the new target group config, and the cutover runbook ready for inspection.
- Read your context and instructions
- Compiled the network change risk
I have reviewed the migration plan for the public API transition from F5 to AWS ALB. The review focuses on the DNS propagation window and target group health check synchronization.
Network Change Risk Review: API Load Balancer Migration
| Category | Status | Finding / Evidence |
|---|---|---|
| DNS Readiness | RISK | TTL is currently 3600s. No evidence of a pre-migration reduction to 60s. High risk of split-traffic during cutover. |
| Target Groups | VERIFIED | ALB target group api-prod-tg matches existing F5 pool members. Health checks configured for /health on port 8080. |
| Security/FW | MISSING | No evidence that the AWS Security Group allows ingress from the WAF CIDR ranges. Potential 403/Timeout risk. |
| Blast Radius | MODERATE | Impacts all mobile clients. Service mesh sidecars (Istio) may require a local DNS cache flush if they bypass system TTL. |
| Rollback | WEAK | Runbook lacks a specific 'Point of No Return'. Missing logic for re-pointing DNS if the ALB exhibits 5XX errors post-cutover. |
Technical Gaps & Questions
- DNS Propagation: Can we confirm a 24-hour lead time for lowering the TTL of
api.example.comto 60 seconds? - Ingress Rules: Is there a Terraform plan showing the Security Group rules for the new ALB?
Internal Auth: The F5 handled SSL termination with a wildcard cert. Will the ALB use ACM or the same imported certificate?
Next steps
- Lower DNS TTL to 60 seconds immediately to prepare for the window.
- Verify Security Group rules against the WAF IP whitelist.
- Define a 5-minute observability window post-cutover before declaring success.
Connects securely to your tools. The creator never sees your data.
About this skill
Network Change Risk Review is a bounded ToolForge Labs workflow. Review planned network and endpoint changes across DNS, load balancers, proxies, firewalls, service discovery, certificates, routing, observability, rollout, and rollback evidence. Works from supplied evidence or workspace files such as documents, logs, configuration, diffs, architecture notes, test summaries, and rollout materials. Produces evidence-backed findings, readiness gaps, risk framing, and practical next actions while preserving existing product/security policy. The skill separates verified facts from assumptions, avoids invented execution claims, and highlights what remains unverified or requires follow-up outside supplied evidence.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for DevOps & Cloud.
Cannot verify production systems, external services, or facts that are not present in supplied evidence. With partial context it returns bounded diagnosis/review, explicit assumptions, and a deterministic validation plan rather than claiming successful execution.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 2 months ago
Permissions
Use a clean branch or a controlled review workspace. Supply repository files, logs, traces, configuration, or evidence needed for the task. Review all patches/findings before merge or operational action; keep production credentials and destructive production actions out of the workflow.