Awesome-omni-skills cloud-devops-v2

Cloud/DevOps Workflow Bundle workflow skill. Use this skill when the user needs Cloud infrastructure and DevOps workflow covering AWS, Azure, GCP, Kubernetes, Terraform, CI/CD, monitoring, and cloud-native development and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

install

source · Clone the upstream repo

git clone https://github.com/diegosouzapw/awesome-omni-skills

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/diegosouzapw/awesome-omni-skills "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/cloud-devops-v2" ~/.claude/skills/diegosouzapw-awesome-omni-skills-cloud-devops-v2 && rm -rf "$T"

manifest: skills/cloud-devops-v2/SKILL.md

Cloud/DevOps Workflow Bundle

Overview

This public intake copy packages

plugins/antigravity-awesome-skills/skills/cloud-devops

from

https://github.com/sickn33/antigravity-awesome-skills

into the native Omni Skills editorial shape without hiding its origin.

Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow.

This intake keeps the copied upstream files intact and uses

metadata.json

plus

ORIGIN.md

as the provenance anchor for review.

Cloud/DevOps Workflow Bundle

Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: Quality Gates, Limitations.

When to Use This Skill

Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request.

Setting up cloud infrastructure
Implementing CI/CD pipelines
Deploying Kubernetes applications
Configuring monitoring and observability
Managing cloud costs
Implementing DevOps practices

Operating Table

Situation	Start here	Why it matters
First-time use	`metadata.json`	Confirms repository, branch, commit, and imported path before touching the copied workflow
Provenance review	`ORIGIN.md`	Gives reviewers a plain-language audit trail for the imported source
Workflow execution	`SKILL.md`	Starts with the smallest copied file that materially changes execution
Supporting context	`SKILL.md`	Adds the next most relevant copied source file without loading the entire package
Handoff decision	`## Related Skills`	Helps the operator switch to a stronger native skill when the task drifts

Workflow

This workflow is intentionally editorial and operational at the same time. It keeps the imported source useful to the operator while still satisfying the public intake standards that feed the downstream enhancer flow.

cloud-architect - Cloud architecture
aws-skills - AWS development
azure-functions - Azure development
gcp-cloud-run - GCP development
terraform-skill - Terraform IaC
terraform-specialist - Advanced Terraform
Design cloud architecture

Imported Workflow Notes

Imported: Workflow Phases

Phase 1: Cloud Infrastructure Setup

Skills to Invoke

```
cloud-architect
```
- Cloud architecture
```
aws-skills
```
- AWS development
```
azure-functions
```
- Azure development
```
gcp-cloud-run
```
- GCP development
```
terraform-skill
```
- Terraform IaC
```
terraform-specialist
```
- Advanced Terraform

Actions

Design cloud architecture
Set up accounts and billing
Configure networking
Provision resources
Set up IAM

Copy-Paste Prompts

Use @cloud-architect to design multi-cloud architecture

Use @terraform-skill to provision AWS infrastructure

Phase 2: Container Orchestration

Skills to Invoke

```
kubernetes-architect
```
- Kubernetes architecture
```
docker-expert
```
- Docker containerization
```
helm-chart-scaffolding
```
- Helm charts
```
k8s-manifest-generator
```
- K8s manifests
```
k8s-security-policies
```
- K8s security

Actions

Design container architecture
Create Dockerfiles
Build container images
Write K8s manifests
Deploy to cluster
Configure networking

Copy-Paste Prompts

Use @kubernetes-architect to design K8s architecture

Use @docker-expert to containerize application

Use @helm-chart-scaffolding to create Helm chart

Phase 3: CI/CD Implementation

Skills to Invoke

```
deployment-engineer
```
- Deployment engineering
```
cicd-automation-workflow-automate
```
- CI/CD automation
```
github-actions-templates
```
- GitHub Actions
```
gitlab-ci-patterns
```
- GitLab CI
```
deployment-pipeline-design
```
- Pipeline design

Actions

Design deployment pipeline
Configure build automation
Set up test automation
Configure deployment stages
Implement rollback strategies
Set up notifications

Copy-Paste Prompts

Use @cicd-automation-workflow-automate to set up CI/CD pipeline

Use @github-actions-templates to create GitHub Actions workflow

Phase 4: Monitoring and Observability

Skills to Invoke

```
observability-engineer
```
- Observability engineering
```
grafana-dashboards
```
- Grafana dashboards
```
prometheus-configuration
```
- Prometheus setup
```
datadog-automation
```
- Datadog integration
```
sentry-automation
```
- Sentry error tracking

Actions

Design monitoring strategy
Set up metrics collection
Configure log aggregation
Implement distributed tracing
Create dashboards
Set up alerts

Copy-Paste Prompts

Use @observability-engineer to set up observability stack

Use @grafana-dashboards to create monitoring dashboards

Phase 5: Cloud Security

Skills to Invoke

```
cloud-penetration-testing
```
- Cloud pentesting
```
aws-penetration-testing
```
- AWS security
```
k8s-security-policies
```
- K8s security
```
secrets-management
```
- Secrets management
```
mtls-configuration
```
- mTLS setup

Actions

Assess cloud security
Configure security groups
Set up secrets management
Implement network policies
Configure encryption
Set up audit logging

Copy-Paste Prompts

Use @cloud-penetration-testing to assess cloud security

Use @secrets-management to configure secrets

Phase 6: Cost Optimization

Skills to Invoke

```
cost-optimization
```
- Cloud cost optimization

database-cloud-optimization-cost-optimize

- Database cost optimization

Actions

Analyze cloud spending
Identify optimization opportunities
Right-size resources
Implement auto-scaling
Use reserved instances
Set up cost alerts

Copy-Paste Prompts

Use @cost-optimization to reduce cloud costs

Phase 7: Disaster Recovery

Skills to Invoke

```
incident-responder
```
- Incident response
```
incident-runbook-templates
```
- Runbook creation
```
postmortem-writing
```
- Postmortem documentation

Actions

Design DR strategy
Set up backups
Create runbooks
Test failover
Document procedures
Train team

Copy-Paste Prompts

Use @incident-runbook-templates to create runbooks

Imported: Cloud Provider Workflows

AWS

Skills: aws-skills, aws-serverless, aws-penetration-testing
Services: EC2, Lambda, S3, RDS, ECS, EKS

Azure

Skills: azure-functions, azure-ai-projects-py, azure-monitor-opentelemetry-py
Services: Functions, App Service, AKS, Cosmos DB

GCP

Skills: gcp-cloud-run
Services: Cloud Run, GKE, Cloud Functions, BigQuery

Imported: Related Workflow Bundles

```
development
```
- Application development
```
security-audit
```
- Security testing
```
database
```
- Database operations
```
testing-qa
```
- Testing workflows

Imported: Overview

Comprehensive cloud and DevOps workflow for infrastructure provisioning, container orchestration, CI/CD pipelines, monitoring, and cloud-native application development.

Imported: Quality Gates

Examples

Example 1: Ask for the upstream workflow directly

Use @cloud-devops-v2 to handle <task>. Start from the copied upstream workflow, load only the files that change the outcome, and keep provenance visible in the answer.

Explanation: This is the safest starting point when the operator needs the imported workflow, but not the entire repository.

Example 2: Ask for a provenance-grounded review

Review @cloud-devops-v2 against metadata.json and ORIGIN.md, then explain which copied upstream files you would load first and why.

Explanation: Use this before review or troubleshooting when you need a precise, auditable explanation of origin and file selection.

Example 3: Narrow the copied support files before execution

Use @cloud-devops-v2 for <task>. Load only the copied references, examples, or scripts that change the outcome, and name the files explicitly before proceeding.

Explanation: This keeps the skill aligned with progressive disclosure instead of loading the whole copied package by default.

Example 4: Build a reviewer packet

Review @cloud-devops-v2 using the copied upstream files plus provenance, then summarize any gaps before merge.

Explanation: This is useful when the PR is waiting for human review and you want a repeatable audit packet.

Best Practices

Treat the generated public skill as a reviewable packaging layer around the upstream repository. The goal is to keep provenance explicit and load only the copied source material that materially improves execution.

Keep the imported skill grounded in the upstream repository; do not invent steps that the source material cannot support.
Prefer the smallest useful set of support files so the workflow stays auditable and fast to review.
Keep provenance, source commit, and imported file paths visible in notes and PR descriptions.
Point directly at the copied upstream files that justify the workflow instead of relying on generic review boilerplate.
Treat generated examples as scaffolding; adapt them to the concrete task before execution.
Route to a stronger native skill when architecture, debugging, design, or security concerns become dominant.

Troubleshooting

Problem: The operator skipped the imported context and answered too generically

Symptoms: The result ignores the upstream workflow in

plugins/antigravity-awesome-skills/skills/cloud-devops

, fails to mention provenance, or does not use any copied source files at all. Solution: Re-open

metadata.json

ORIGIN.md

, and the most relevant copied upstream files. Load only the files that materially change the answer, then restate the provenance before continuing.

Problem: The imported workflow feels incomplete during review

Symptoms: Reviewers can see the generated

SKILL.md

, but they cannot quickly tell which references, examples, or scripts matter for the current task. Solution: Point at the exact copied references, examples, scripts, or assets that justify the path you took. If the gap is still real, record it in the PR instead of hiding it.

Problem: The task drifted into a different specialization

Symptoms: The imported skill starts in the right place, but the work turns into debugging, architecture, design, security, or release orchestration that a native skill handles better. Solution: Use the related skills section to hand off deliberately. Keep the imported provenance visible so the next skill inherits the right context instead of starting blind.

Related Skills

```
@chrome-extension-developer-v2
```
- Use when the work is better handled by that native specialization after this imported skill establishes context.
```
@churn-prevention-v2
```
- Use when the work is better handled by that native specialization after this imported skill establishes context.
```
@circleci-automation-v2
```
- Use when the work is better handled by that native specialization after this imported skill establishes context.
```
@cirq-v2
```
- Use when the work is better handled by that native specialization after this imported skill establishes context.

Additional Resources

Use this support matrix and the linked files below as the operator packet for this imported skill. They should reflect real copied source material, not generic scaffolding.

Resource family	What it gives the reviewer	Example path
`references`	copied reference notes, guides, or background material from upstream	`references/n/a`
`examples`	worked examples or reusable prompts copied from upstream	`examples/n/a`
`scripts`	upstream helper scripts that change execution or validation	`scripts/n/a`
`agents`	routing or delegation notes that are genuinely part of the imported package	`agents/n/a`
`assets`	supporting assets or schemas copied from the source package	`assets/n/a`

Imported Reference Notes

Imported: Limitations

Use this skill only when the task clearly matches the scope described above.
Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.