Skip to content
Back to skills

Infrastructure Devops

ASecurity

Design and maintain deployment, runtime, CI/CD, containers, workers, scheduling, and operational infrastructure using platform-agnostic principles.

  • 3 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 2, 2026
ai-agentsdevopsci/cd

Security analysis

A100/100

Scanned September 2, 2026

npx -y skills add soden46/engineer-flow --skill infrastructure-devops --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Infrastructure Devops?

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

Security grade badge for Infrastructure Devops
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/soden46-infrastructure-devops/badge)](https://www.skillsdirectory.com/skills/soden46-infrastructure-devops)

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
---
name: infrastructure-devops
description: Design and maintain deployment, runtime, CI/CD, containers, workers, scheduling, and operational infrastructure using platform-agnostic principles.
metadata:
  internal: true
---

# infrastructure-devops

Use this skill for deployment, CI/CD, containers, scheduling, workers, runtime configuration, health checks, and operational automation.

## Principles

Prefer reproducible and observable deployment processes.

Separate configuration from application source where appropriate.

Automated workflows should fail clearly and avoid silently publishing broken artifacts.

Consider:

- build reproducibility
- health checks
- restart behavior
- rollout strategy
- rollback strategy
- resource limits
- secret handling
- logs
- monitoring

Background and scheduled workloads should define:

- ownership
- retries
- duplicate execution behavior
- concurrency
- failure handling

Do not assume local development behavior represents production behavior.

## Adaptation

Use project evidence to determine the actual language, framework, runtime, and existing conventions.

When stack-specific implementation guidance is needed, prefer project evidence, native framework or language mechanisms, and relevant user-installed specialist skills. Technology-specific guidance must not redefine or weaken the core engineering requirement.

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…