Cloud & DevOps Engineering

Software development skill, available on Zeplik

Cloud & DevOps Engineering is a ready-to-run software development skill on Zeplik. Not for cloud bill reduction (use cost-optimization) or GitHub Actions YAML (use github-actions-templates). Ask in plain language and Zeplik applies the skill's method for you inside the conversation, on whichever AI model you prefer.

The Cloud & DevOps Engineering skill loads automatically when your request matches it, or you can invoke it directly by typing /cloud-devops in any chat. It works with attachments, connectors, and any model that supports the task, so you get the same expert method every time without setting anything up.

What the Cloud & DevOps Engineering skill can do

Try these prompts on Zeplik

Pick a prompt to open it in the Zeplik app. If you are not signed in yet, your prompt is waiting for you the moment you do.

How the Cloud & DevOps Engineering skill works

/cloud-devops

Umbrella skill for cloud infrastructure and platform operations: designing infrastructure as code across AWS, GCP, Azure, and OCI, running Kubernetes in production, building deployment pipelines, wiring up service meshes, and standing up observability. The body of this skill is a dispatch table; the real depth lives in references/. Pick the reference(s) that match the user's intent, read them, then answer. This lane is about building and operating infrastructure -- not about reducing cloud spend (that is cost-optimization) and not about authoring GitHub Actions workflow YAML (that is github-actions-templates).

Dispatch table

IntentReference
Multi-stage CI/CD pipeline design, approval gates, zero-downtime deploy strategyreferences/deployment-pipeline-design.md (+ --details, --advanced-strategies)
GitLab CI pipelines, caching, runners, multi-stage workflowsreferences/gitlab-ci-patterns.md
On-prem to cloud connectivity, VPN, Direct Connect / dedicated linksreferences/hybrid-cloud-networking.md (+ --direct-connect)
Istio routing, load balancing, circuit breakers, canary traffic policiesreferences/istio-traffic-management.md
Linkerd setup, lightweight mesh, mesh traffic policiesreferences/linkerd-patterns.md
Mutual TLS, zero-trust service-to-service auth, certificate managementreferences/mtls-configuration.md (+ --details)
Multi-cloud service selection and integration across AWS/Azure/GCP/OCIreferences/multi-cloud-architecture.md (+ --multi-cloud-patterns, --service-comparison)
Mesh metrics, tracing, and visualization for service meshesreferences/service-mesh-observability.md (+ --details)
Reusable Terraform modules, IaC structure and best practicesreferences/terraform-module-library.md (+ --aws-modules, --oci-modules)
GitOps with ArgoCD or Flux, declarative K8s delivery, reconciliationreferences/gitops-workflow.md (+ --argocd-setup, --sync-policies)
Helm chart structure, templating, packaging K8s appsreferences/helm-chart-scaffolding.md (+ --chart-structure, --details)
Kubernetes manifests: Deployments, Services, ConfigMaps, Secretsreferences/k8s-manifest-generator.md (+ --deployment-spec, --service-spec, --details)
K8s security: NetworkPolicy, Pod security, RBACreferences/k8s-security-policies.md (+ --rbac-patterns)
Distributed tracing with Jaeger/Tempo, cross-service request trackingreferences/distributed-tracing.md (+ --details)
Grafana dashboard design and managementreferences/grafana-dashboards.md
Prometheus setup, scrape configs, recording rules, alertingreferences/prometheus-configuration.md (+ --details)
SLIs, SLOs, error budgets, reliability alertingreferences/slo-implementation.md (+ --details)

How to work

  1. Identify the intent and read the matching reference file(s) before answering; load the -- companion files when the main reference points to them for depth.
  2. If the target platform, cloud provider, or tool is ambiguous (for example "set up a mesh" without naming Istio or Linkerd, or "IaC" without a cloud), ask ONE clarifying question before going deep.
  3. Produce concrete artifacts for the user: full Terraform modules, Helm charts, manifests, pipeline definitions, or Prometheus configs they can paste into their repo. When a step requires access you do not have (a cluster, a cloud account), walk the user through the exact commands and what output to expect, and ask them to paste results back if verification matters.
  4. Combine references when the question spans areas (for example a GitOps rollout with canary traffic shifting touches gitops-workflow plus istio-traffic-management).
  5. Redirect out-of-lane requests: cloud bill reduction goes to cost-optimization; GitHub Actions workflow YAML goes to github-actions-templates.

Usage

/cloud-devops $ARGUMENTS

How to use the Cloud & DevOps Engineering skill

  1. Sign in to Zeplik

    Create a free Zeplik account or sign in. New accounts start with free credits, so you can try the Cloud & DevOps Engineering skill right away.

  2. Describe your software development task

    Ask in plain language, or type /cloud-devops to invoke the skill directly. Zeplik recognizes the Cloud & DevOps Engineering skill and applies its method.

  3. Review and refine the result

    Zeplik returns a clear, structured answer. Ask follow-ups in the same chat to refine it or take the next step.

Source and credit

Author
anthropic
License
MIT

Adapted from the open-source wshobson/agents project and tuned to run natively on Zeplik. View source on GitHub.

Frequently asked questions

What is the Cloud & DevOps Engineering skill?
Cloud & DevOps Engineering is a ready-to-run software development skill on Zeplik. Not for cloud bill reduction (use cost-optimization) or GitHub Actions YAML (use github-actions-templates). Ask in plain language and Zeplik applies the skill's method for you inside the conversation, on whichever AI model you prefer.
How do I use Cloud & DevOps Engineering on Zeplik?
Sign in to Zeplik and ask in plain language, or type /cloud-devops in any chat to invoke it directly. The skill applies its method and returns a result you can refine in the same conversation.
Which AI model does the Cloud & DevOps Engineering skill use?
Any model you choose. Zeplik works across every model in one chat, so the Cloud & DevOps Engineering skill runs on your preferred model for the task.
Where does the Cloud & DevOps Engineering skill come from?
The Cloud & DevOps Engineering skill is adapted from the open-source wshobson/agents project (MIT) and tuned to run natively on Zeplik. The original source is linked on this page.
How much does the Cloud & DevOps Engineering skill cost?
Using the skill is free to start. You only spend Zeplik credits when the assistant runs, and new accounts begin with free credits.

Related software development skills

More on Zeplik

Try Cloud & DevOps Engineering on Zeplik

Every model, one chat. Bring the Cloud & DevOps Engineering skill into your next conversation and let the assistant do the work.

Browse all skills
Cloud & DevOps Engineering - Software development skill for Zeplik AI | Zeplik Chat