kubernetes-operations

Estrelas10

Forks0

Atualizado5 de julho de 2026 às 10:55

Use for Kubernetes deployment, manifests, Helm, Kustomize, operations, scaling, storage, networking, RBAC, NetworkPolicy, Pod Security, rollout planning, rollback, and cluster troubleshooting.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Fonte

ashermahonin

ashermahonin/agentic-skills

Abrir repositório GitHub Ver repositórios do creator

Download

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Administradores de redes e sistemas de computadorInformática e Matemática·SOC 15-1244

Explorador de arquivos

3 arquivos

SKILL.md

readonly

name	kubernetes-operations
description	Use for Kubernetes deployment, manifests, Helm, Kustomize, operations, scaling, storage, networking, RBAC, NetworkPolicy, Pod Security, rollout planning, rollback, and cluster troubleshooting.

Kubernetes Operations

Role

You handle Kubernetes changes with production discipline: validate APIs, design the smallest safe workload change, make rollout behavior explicit, and keep troubleshooting grounded in cluster evidence.

Start By

Read references/workflow.md.
Identify cluster distribution, version, delivery method, namespace, ingress, CNI, CSI, and security constraints.
Verify current Kubernetes, Helm, Kustomize, chart, controller, or provider documentation before writing manifests or commands.

Procedure

Classify the task: deploy, operate, secure, debug, migrate, scale, or review.
Determine blast radius: namespace, workload, cluster-wide resource, node pool, network path, or storage.
Design workload type, service exposure, rollout strategy, probes, resources, security context, placement, and config/secret separation.
Implement manifests, Helm values, Kustomize patches, or operational commands with explicit versions and ownership labels.
Validate with schema checks, dry-run/server-side apply, helm lint/template, kustomize build, rollout checks, and smoke tests when available.

Principal-Level Defaults

Follow ../../routing/principal-operating-model.md before moving from analysis to implementation.
Use Context7 MCP for current cloud, Kubernetes, IaC, CI/CD, container, observability, security, network, API, CLI, provider, and configuration documentation whenever the task depends on external technology behavior.
Keep a decision trace: facts, assumptions, options considered, tradeoffs, selected path, validation evidence, and rollback or follow-up.
Escalate irreversible, security-sensitive, data-migration, production, or cross-boundary choices before write-heavy work.

Output Artifacts

Provide Kubernetes context, documentation validation status, proposed design, YAML/Helm/Kustomize changes, validation commands, rollback notes, and assumptions.

Quality Bar

Use current API versions for the target cluster.
Include requests/limits, probes, rollout strategy, and security context where relevant.
Avoid root containers, broad RBAC, and latest image tags in production examples.
Treat storage, DNS, ingress, TLS, and NetworkPolicy as first-class design inputs.

Handoff

For image build work, add container-platforms. For delivery automation, add cicd-automation. For cluster exposure, VPN, or private routing, add network-vpn-security. For secrets or RBAC hardening, add security-secrets.

References

references/workflow.md for detailed Kubernetes workflow and verification checklist.

Mais deste repositório

mesmo repositório

accessibility-audit

ashermahonin/agentic-skills

Audit any product surface against accessibility standards: WCAG 2.2 AA for web, Apple UIKit/SwiftUI Accessibility for iOS, Android TalkBack/AccessibilityService for Android, Microsoft UIA for Windows, AT-SPI for Linux, game-specific readability and remappable-controls patterns, and voice/chat AI surfaces with appropriate alternative modes. Produces a per-criterion status, automated test suggestions, manual test scripts, screen-reader transcripts, contrast measurements, and a release-gate verdict that names the fixed and outstanding findings. Use after ux-design and before release on every surface with user interaction.

2026-07-0510

agent-harness-architect

ashermahonin/agentic-skills

Design or review the operational harness around single-agent, multi-agent, and tool-using AI systems. Use when building agent platforms, routing layers, tool interfaces, memory systems, evaluation harnesses, human checkpoints, permission boundaries, cost controls, or agent-computer interfaces that must remain observable, testable, and safe under real project work.

2026-07-0510

ai-pdlc

ashermahonin/agentic-skills

Run an AI-augmented Product Development Lifecycle that treats every phase as a hypothesis to test, not a deliverable to push: research, hypothesis, plan-by-phases, prototype, validate, implement under TDD, harden against the matching security track (OWASP/MASVS) and CVE risk, and ship with rollback and post-launch evaluation. Use as the strategic spine when a project is greenfield, a brownfield refactor, an experiment, or a feature whose value is not yet proven; cooperates with sdlc-orchestrator (operational chain) and hypothesis-validator (evidence).

2026-07-0510

analyze-codebase

ashermahonin/agentic-skills

Analyze an existing repository in read-only mode to reconstruct current behavior, architecture, dependency clusters, build and test health, hotspots, tech debt, ownership boundaries, integration points, and current-vs-target gaps. Use for existing-product improvement, migration planning, code archaeology, risky refactors, unfamiliar repositories, or artifacts `80-current-state-scan.md` through `85-migration-plan.md` before writing code.

2026-07-0510

architecture-review

ashermahonin/agentic-skills

Design or review software architecture using system context, container, component, runtime, deployment, data, API, integration, crosscutting concepts, and ADR artifacts. Use before large implementation, service-boundary changes, infrastructure changes, API or data contract changes, migrations, reliability work, security-sensitive design, or architecture artifacts `14-system-context.md` through `22-adr-index.md`.

2026-07-0510

cicd-automation

ashermahonin/agentic-skills

Use for CI/CD, pipeline automation, GitHub Actions, GitLab CI, Jenkins, Argo, Azure DevOps, build-test-scan-package-deploy flows, release orchestration, protected environments, approvals, and rollback.

2026-07-0510

name	kubernetes-operations
description	Use for Kubernetes deployment, manifests, Helm, Kustomize, operations, scaling, storage, networking, RBAC, NetworkPolicy, Pod Security, rollout planning, rollback, and cluster troubleshooting.

Kubernetes Operations

Role

Start By

Read references/workflow.md.
Identify cluster distribution, version, delivery method, namespace, ingress, CNI, CSI, and security constraints.
Verify current Kubernetes, Helm, Kustomize, chart, controller, or provider documentation before writing manifests or commands.

Procedure

Classify the task: deploy, operate, secure, debug, migrate, scale, or review.
Determine blast radius: namespace, workload, cluster-wide resource, node pool, network path, or storage.
Design workload type, service exposure, rollout strategy, probes, resources, security context, placement, and config/secret separation.
Implement manifests, Helm values, Kustomize patches, or operational commands with explicit versions and ownership labels.
Validate with schema checks, dry-run/server-side apply, helm lint/template, kustomize build, rollout checks, and smoke tests when available.

Principal-Level Defaults

Follow ../../routing/principal-operating-model.md before moving from analysis to implementation.
Use Context7 MCP for current cloud, Kubernetes, IaC, CI/CD, container, observability, security, network, API, CLI, provider, and configuration documentation whenever the task depends on external technology behavior.
Keep a decision trace: facts, assumptions, options considered, tradeoffs, selected path, validation evidence, and rollback or follow-up.
Escalate irreversible, security-sensitive, data-migration, production, or cross-boundary choices before write-heavy work.

Output Artifacts

Provide Kubernetes context, documentation validation status, proposed design, YAML/Helm/Kustomize changes, validation commands, rollback notes, and assumptions.

Quality Bar

Use current API versions for the target cluster.
Include requests/limits, probes, rollout strategy, and security context where relevant.
Avoid root containers, broad RBAC, and latest image tags in production examples.
Treat storage, DNS, ingress, TLS, and NetworkPolicy as first-class design inputs.

Handoff

References

references/workflow.md for detailed Kubernetes workflow and verification checklist.