Skip to content
Back to skills

Infra Operations

ASecurity

Run infrastructure operations with controlled execution, operational evidence, and clear incident-safe handoffs.

  • 72 stars
  • 0 votes
  • 0 copies
  • 3 views
  • Added September 5, 2026
devopsgo

Security analysis

A100/100

Scanned September 30, 2026

npx -y skills add devton/agentic-workflow-blueprint --skill infra-operations --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Infra Operations?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Infra Operations
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/devton-infra-operations/badge)](https://www.skillsdirectory.com/skills/devton-infra-operations)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
## agentic-workflows-blueprint.workflow.infra-operations

### Goal

Run infrastructure operations with controlled execution, operational evidence, and clear incident-safe handoffs.

### Scope

- Applies to: operational infrastructure changes across compute, storage, network, runtime services, and platform dependencies.
- Does not cover: product-only code refactors with no operational impact.

### Triggers

- "Run this infrastructure change"
- "Prepare infra change runbook"
- "Operate rollout with rollback checkpoints"
- "Create infra operations contract"

### Inputs

- `environment`
- `changeRequest` (ticket, owner, objective)
- `changeWindow`
- `serviceDependencies`
- `healthChecks`
- `rollbackPlan`

### Invariants

- No production mutation without pre-change health baseline.
- Every step must emit evidence (command output, dashboard snapshots, or logs).
- Rollback checkpoints are mandatory for high-risk steps.
- Incident escalation path must be known before execution.

### Procedure

1. Validate readiness: approvals, maintenance window, dependency ownership, and communication channel.
2. Capture baseline health and capacity metrics.
3. Execute change in incremental phases with explicit checkpoints.
4. Run health checks after each phase.
5. If any checkpoint fails, trigger rollback and incident communication.
6. Finalize post-change summary with completed actions, open risks, and next monitoring actions.

### Outputs

- Infra operations execution log.
- Checkpoint results and health evidence.
- Rollback or success closure note.
- Handoff note for `document` and `review`.

### Review gate

- [ ] Change window, owner, and escalation path are explicit.
- [ ] Baseline and post-change evidence are attached.
- [ ] Rollback checkpoints are complete.
- [ ] Handoff contains residual risk and monitoring instructions.

### References

- `../../SKILL.md`
- `../network-engineering/SKILL.md`
- `../document/SKILL.md`

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.