kubernetes-ops

Name: kubernetes-ops
Author: cowork-os

github.com/cowork-osCloud & DevOps52645 installsUpdated today

About kubernetes-ops

A Kubernetes operations skill for producing kubectl commands, manifests, Helm operations, and debugging guidance. It is intended for cluster management and deployment tasks involving Kubernetes resources.

Key features

01Generate kubectl commands
02Create Kubernetes manifests
03Guide Helm operations
04Support RBAC and deployment strategies
05Troubleshoot cluster issues

Use cases

01Debug pods, deployments, or services
02Manage ingress or RBAC
03Prepare Kubernetes deployments

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/cowork-os/cowork-os --skill kubernetes-ops

After installing, type/kubernetes-opsin Claude Code to confirm it loaded.

Bundled filesreferences/full-guidance.mdscripts/.gitkeep

Details

From the project README

Kubernetes Operations

Purpose

Kubernetes cluster operations: kubectl commands, manifest generation, Helm charts, RBAC, debugging, and deployment strategies.

Routing

Use when: Use when the user asks about Kubernetes, k8s, kubectl, pods, deployments, services, ingress, Helm charts, RBAC, container orchestration, or cluster management.
Do not use when: Do not use for Docker Compose (use docker-compose-ops), Terraform IaC (use terraform-ops), or general cloud migration (use cloud-migration).
Outputs: kubectl commands, Kubernetes manifests (YAML), Helm operations, and debugging guidance.
Success criteria: Returns valid Kubernetes manifests or kubectl commands that can be applied to a cluster.

Trigger Examples

Positive

Use the kubernetes-ops skill for this request.
Help me with kubernetes operations.
Use when the user asks about Kubernetes, k8s, kubectl, pods, deployments, services, ingress, Helm charts, RBAC, container orchestration, or cluster management.
Kubernetes Operations: provide an actionable result.

Negative

Do not use for Docker Compose (use docker-compose-ops), Terraform IaC (use terraform-ops), or general cloud migration (use cloud-migration).
Do not use kubernetes-ops for unrelated requests.
This request is outside kubernetes operations scope.
This is conceptual discussion only; no tool workflow is needed.

Runtime Prompt

Current runtime prompt length: 898 characters.
Runtime prompt is defined directly in ../kubernetes-ops.json.

Comments

Markdown supported

Details

Author: cowork-os
Repository: cowork-os/cowork-os
Category: Cloud & DevOps
Installs: 45
GitHub stars: 526

Report

More skills

All skills

lark-apps

open.feishu.cn

757.8k

Develop and host Miaoda (Spark/Miaoda) apps: app creation, local full-stack development, cloud generation and iteration, creative design (UI mockups / interactive prototypes / wireframes / landing pages / dashboards / slide decks / visual exploration), integration of AI-related capabilities, Feishu platform capabilities, or other external capabilities; log/Trace/monitoring metric/PV/UV queries; environment variable management; app collaborators and collaboration permissions; app roles and members; and automation triggers (scheduled / record changes / Webhook / Feishu approvals). Use when users want to develop or create a system, tool, platform, or app; develop locally or in the cloud, modify, deploy, publish, launch, or get a shareable link; create a page or website with HTML and deploy it to Miaoda; design, create a mockup, prototype, wireframe, PPT, deck, or visual exploration; or mention Miaoda/Spark/Miaoda apps (links like `/app/app_xxx` or `/page/<token>`, runtime domains like *.aiforce.cloud), app databases, app file storage, open API Keys, visibility, app collaborators/developer permissions, app roles/role members, production logs, API request volume, error volume, latency, traffic, environment variables, or setting up automation tasks, scheduled triggers, or approval-triggered automation for Miaoda apps. Not for regular cloud drive file uploads (lark-drive), Feishu document editing (lark-doc), or native slide creation (lark-slides).

azure-prepare

github.com/microsoft

603.1k

Prepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Terraform), and Dockerfiles for the Azure Developer CLI (azd) workflow. USE ONLY when the user explicitly wants to use azd as the deployment tool, or the project already has an azure.yaml file. DO NOT USE FOR: non-azd deployments, Python App Service code-only deploys (use python-appservice-deploy), or cross-cloud migration (use azure-cloud-migrate). WHEN: prepare app for azd, create azure.yaml, set up azd infrastructure, modernize app for Azure with azd, deploy with azd, function app, timer trigger, service bus trigger, event-driven function, managed identity, generate Bicep, generate Terraform, create and deploy to Azure.

azure-ai

github.com/microsoft

602.4k

Use for Azure AI: Search, Speech, OpenAI, Document Intelligence. Helps with search, vector/hybrid search, speech-to-text, text-to-speech, transcription, OCR. WHEN: AI Search, query search, vector search, hybrid search, semantic search, speech-to-text, text-to-speech, transcribe, OCR, convert text to speech.

azure-deploy

github.com/microsoft

602.1k

Execute Azure deployments for already-prepared applications that have an existing .azure/deployment-plan.md and infrastructure files. Do not use this skill when the user asks to create a new application; use azure-prepare instead. This skill runs azd up, azd deploy, terraform apply and az deployment commands with built-in error recovery. Requires .azure/deployment-plan.md from azure-prepare and validated status from azure-validate. WHEN: "run azd up", "run azd deploy", "execute deployment", "push to production", "push to cloud", "go live", "ship it", "bicep deploy", "terraform apply", "publish to Azure", "launch on Azure". DO NOT USE WHEN: "create and deploy", "build and deploy", "create a new app", "set up infrastructure", "create and deploy to Azure using Terraform"; use azure-prepare for these.