Devops Deployment logo

Devops Deployment

Community
yonatangross
devops-deployment

Use when setting up CI/CD pipelines, containerizing applications, deploying to Kubernetes, or writing infrastructure as code. DevOps & Deployment covers GitHub Actions, Docker, Helm, and Terraform patterns.

Overview

Publisheryonatangross
Repositoryorchestkit
Skill namedevops-deployment
Stars
298
Forks
35
Bundled files
27
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 27 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by yonatangross on GitHub. Read the source before you install it.

Installation

Install the Devops Deployment AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/yonatangross/orchestkit/tree/main/plugins/ork/skills/devops-deployment
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/yonatangross/orchestkit.git /tmp/orchestkit
mkdir -p .claude/skills
cp -r /tmp/orchestkit/plugins/ork/skills/devops-deployment .claude/skills/devops-deployment
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Devops Deployment in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Devops Deployment on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Devops Deployment is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

DevOps & Deployment Skill

Comprehensive frameworks for CI/CD pipelines, containerization, deployment strategies, and infrastructure automation.

Note: If disableSkillShellExecution is enabled (CC 2.1.91), the Docker install check won't run. Verify Docker is available for container operations: docker --version.

Overview

  • Setting up CI/CD pipelines
  • Containerizing applications
  • Deploying to Kubernetes or cloud platforms
  • Implementing GitOps workflows
  • Managing infrastructure as code
  • Planning release strategies

Pipeline Architecture

┌──────────┐ ┌──────────┐ ┌──────────┐ ┌──────────┐
│ Code     │─>│ Build    │─>│ Test     │─>│ Deploy   │
│ Commit   │ │ Lint     │ │ Scan     │ │ Release  │
└──────────┘ └──────────┘ └──────────┘ └──────────┘
  triggers     artifacts    reports      monitoring

Key Concepts

CI/CD Pipeline Stages

  1. Lint & Type Check - Code quality gates
  2. Unit Tests - Test coverage with reporting
  3. Security Scan - npm audit + Trivy vulnerability scanner
  4. Build & Push - Docker image to container registry
  5. Deploy Staging - Environment-gated deployment
  6. Deploy Production - Manual approval or automated

Container Best Practices

Multi-stage builds minimize image size:

  • Stage 1: Install production dependencies only
  • Stage 2: Build application with dev dependencies
  • Stage 3: Production runtime with minimal footprint

Security hardening:

  • Non-root user (uid 1001)
  • Read-only filesystem where possible
  • Health checks for orchestrator integration

Kubernetes Deployment

Essential manifests:

  • Deployment with rolling update strategy
  • Service for internal routing
  • Ingress for external access with TLS
  • HorizontalPodAutoscaler for scaling

Security context:

  • runAsNonRoot: true
  • allowPrivilegeEscalation: false
  • readOnlyRootFilesystem: true
  • Drop all capabilities

Deployment Strategies

StrategyUse CaseRisk
RollingDefault, gradual replacementLow - automatic rollback
Blue-GreenInstant switch, easy rollbackMedium - double resources
CanaryProgressive traffic shiftLow - gradual exposure

Rolling Update (Kubernetes default):

yaml
strategy:
  type: RollingUpdate
  rollingUpdate:
    maxSurge: 25%
    maxUnavailable: 0  # Zero downtime

Secrets Management

Use External Secrets Operator to sync from cloud providers:

  • AWS Secrets Manager
  • HashiCorp Vault
  • Azure Key Vault
  • GCP Secret Manager

References

Docker Patterns

Load: Read("references/docker-patterns.md")

Key topics covered:

  • Multi-stage build examples with 78% size reduction
  • Layer caching optimization
  • Security hardening (non-root, health checks)
  • Trivy vulnerability scanning
  • Docker Compose development setup

OrchestKit Delta (house rules)

Load: Read("references/ork-delta.md")

Key topics covered:

  • CI concurrency groups, the sub-5-minute feedback budget, path filtering
  • Service-container health gating, SHA-pinned deploys, CDN invalidation order
  • Kubernetes probe budget, request/limit baseline, PodDisruptionBudget floor
  • External Secrets refresh interval, ArgoCD prune plus selfHeal, Terraform state locking
  • Alert thresholds with dwell windows, request-id log binding, rollback rehearsal

Railway Deployment

Load: Read("rules/railway-deployment.md")

Key topics covered:

  • railway.json configuration, Nixpacks builds
  • Environment variable management, database provisioning
  • Multi-service setups, Railway CLI workflows
  • References: references/railway-json-config.md, references/nixpacks-customization.md, references/multi-service-setup.md

Deployment Strategies

Load: Read("references/deployment-strategies.md")

Key topics covered:

  • Rolling deployment (maxUnavailable / maxSurge)
  • Blue-green deployment (service-selector switch and rollback)
  • Canary releases (replica-ratio traffic split)

Upstream coverage (do not restate)

This skill wraps third-party products. Vendor mechanics are not restated here; fetch them from the source below. Where a row says "house subset stays in X", that file keeps only OrchestKit's threshold, config or ordering decision, not the vendor tutorial.

TopicFetch from
GitHub Actions workflow syntax, matrix builds, artifact upload/download, cache mechanicshttps://docs.github.com/en/actions/reference/workflows-and-actions/workflow-syntax (house cache-key subset stays in rules/devops-ci-caching.md)
Trigger filters (on.push.paths, schedules, workflow_dispatch)https://docs.github.com/en/actions/how-tos/write-workflows/choose-when-workflows-run/trigger-a-workflow
Service containers for integration testshttps://docs.github.com/en/actions/tutorials/use-containerized-services/use-docker-service-containers
Deployment environments and approval gateshttps://docs.github.com/en/actions/how-tos/deploy/configure-and-manage-deployments/manage-environments
Protected branches and required status checkshttps://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/about-protected-branches (house approval counts stay in rules/devops-branch-protection.md)
Kubernetes probe semantics and every probe fieldhttps://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/ (house probe numbers stay in references/ork-delta.md)
Requests, limits, quotas and QoS classeshttps://kubernetes.io/docs/concepts/configuration/manage-resources-containers/ (house baseline stays in references/ork-delta.md)
PodDisruptionBudget semantics and eviction APIhttps://kubernetes.io/docs/tasks/run-application/configure-pdb/ (house minAvailable floor stays in references/ork-delta.md)
StatefulSets, ordinal identity, volumeClaimTemplateshttps://kubernetes.io/docs/concepts/workloads/controllers/statefulset/
Helm chart authoring, templating and values fileshttps://helm.sh/docs/topics/charts/ (the chart directory layout we use stays in references/checklists-and-templates.md)
External Secrets Operator CRD fields and backendshttps://external-secrets.io/latest/api/externalsecret/ (house refresh/creation policy stays in references/ork-delta.md)
ArgoCD automated sync, prune and self-healhttps://argo-cd.readthedocs.io/en/stable/user-guide/auto_sync/ (house retry/backoff stays in references/ork-delta.md)
Terraform S3 backend and state lockinghttps://developer.hashicorp.com/terraform/language/backend/s3 (house backend config stays in references/ork-delta.md)
Terraform module composition and variable fileshttps://developer.hashicorp.com/terraform/language/modules
Alembic revision, upgrade and downgrade CLIhttps://alembic.sqlalchemy.org/en/latest/tutorial.html (the zero-downtime migration ordering stays in rules/devops-db-migrations.md)
Prometheus client instrumentation (Counter, Histogram, exposition)https://prometheus.github.io/client_python/
PromQL functions (rate, histogram_quantile) for dashboardshttps://prometheus.io/docs/prometheus/latest/querying/functions/
Prometheus alerting rule syntaxhttps://prometheus.io/docs/prometheus/latest/configuration/alerting_rules/ (house thresholds and dwell windows stay in references/ork-delta.md)
OpenTelemetry FastAPI auto-instrumentation and manual spanshttps://opentelemetry-python-contrib.readthedocs.io/en/latest/instrumentation/fastapi/fastapi.html
structlog context bindinghttps://www.structlog.org/en/stable/contextvars.html (the bind-then-call ordering stays in references/ork-delta.md)
Trivy severity filtering and scan configurationhttps://trivy.dev/latest/docs/configuration/filtering/ (the house image-scan CI wiring stays in references/docker-patterns.md, the weekly-scan schedule and severity floor in references/ork-delta.md)
CloudFront invalidation semantics and costhttps://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/Invalidation.html (the sync-then-invalidate order stays in references/ork-delta.md)
Pre-launch security, load-testing and monitoring checklistsork:security-patterns, ork:testing-perf, ork:monitoring-observability (the deploy-day checklist stays in references/checklists-and-templates.md)

Deployment Checklist & Templates

Load: Read("references/checklists-and-templates.md") for pre/during/post-deployment checklists, Helm chart structure, and template reference table.


Related Skills

  • ork:security-patterns - Security scanning and hardening patterns for CI/CD pipelines
  • ork:monitoring-observability - Prometheus, Grafana and alerting for deployed applications
  • ork:database-patterns - Python/Alembic migration workflow for backend deployments
  • portless (upstream) - Named .localhost URLs for multi-service local dev (portless alias api 8080)

Key Decisions

DecisionChoiceRationale
Container userNon-root (uid 1001)Security best practice, required by many orchestrators
Deployment strategyRolling update (default)Zero downtime, automatic rollback, resource efficient
Secrets managementExternal Secrets OperatorSyncs from cloud providers, GitOps compatible
Health checksSeparate startup/liveness/readinessPrevents premature traffic, enables graceful shutdown

Capability Details

Load: Read("references/capability-details.md") for full keyword index and problem-solution mapping across all 6 capabilities (ci-cd, docker, kubernetes, infrastructure-as-code, deployment-strategies, observability).

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Devops Deployment AI skill do?

Use when setting up CI/CD pipelines, containerizing applications, deploying to Kubernetes, or writing infrastructure as code. DevOps & Deployment covers GitHub Actions, Docker, Helm, and Terraform patterns.

Why use Devops Deployment on TypingMind?

Because you install it once and use it with any model. Devops Deployment is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Devops Deployment in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/yonatangross/orchestkit/tree/main/plugins/ork/skills/devops-deployment. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Devops Deployment?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Devops Deployment?

As many as you like. As long as a model supports skills, you can use Devops Deployment with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Devops Deployment AI skill free?

Yes. It is published on GitHub by yonatangross under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇