kubernetes-basics
Kubernetes Basics
Overview
Use this skill to define a deployable Kubernetes baseline that is reproducible and operationally verifiable.
Scope Boundaries
- Use this skill when the task matches the trigger condition described in
description. - Do not use this skill when the primary task falls outside this skill's domain.
Shared References
- Service discovery and probe rules:
references/service-discovery-and-probe-rules.md
Templates And Assets
- Baseline workload manifest:
assets/workload-baseline-template.yaml
- Basics verification checklist:
assets/k8s-basics-checklist.md
Inputs To Gather
- Target workloads and service exposure model.
- Namespace and resource-boundary requirements.
- Health signal requirements and dependency expectations.
- Rollout and rollback expectations.
Deliverables
- Baseline workload/service manifest set.
- Probe and discovery policy aligned with runtime behavior.
- Namespace/resource boundary decisions.
- Deployment verification checklist and evidence.
Workflow
- Define workload/service baseline using
assets/workload-baseline-template.yaml. - Apply probe and discovery guidance from
references/service-discovery-and-probe-rules.md. - Align namespace/resource boundaries with ownership and blast radius.
- Validate deployment behavior via
assets/k8s-basics-checklist.md. - Publish residual risks and follow-up actions.
Quality Standard
- Baseline manifests are declarative and reviewable.
- Service routing and probe semantics are explicit.
- Readiness reflects true traffic-safety conditions.
- Rollback path is clear before production rollout.
Failure Conditions
- Stop when baseline workloads cannot be deployed reliably on target cluster.
- Stop when probes do not represent meaningful application health.
- Escalate when namespace/resource boundaries remain ambiguous.
More from kentoshimizu/sw-agent-skills
graph-algorithms
Graph algorithm workflow for modeling entities/relations and selecting traversal, path, ordering, or flow strategies. Use when correctness or performance depends on graph representation and algorithm choice; do not use for schema-only modeling or deployment topology planning.
14bash-style-guide
Style, review, and refactoring standards for Bash shell scripting. Trigger when `.sh` files, files with `#!/usr/bin/env bash` or `#!/bin/bash`, or CI workflow blocks with `shell: bash` are created, modified, or reviewed and Bash-specific quality controls (quoting safety, error handling, portability, readability) must be enforced. Do not use for generic POSIX `sh`, PowerShell, or language-specific application style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.
11architecture-clean-architecture
Clean Architecture workflow for enforcing dependency direction, stable domain boundaries, and use-case-centered application design. Use when teams must separate business rules from frameworks and delivery mechanisms; do not use for isolated module cleanup without boundary implications.
11powershell-style-guide
Style, review, and refactoring standards for PowerShell scripting. Trigger when `.ps1`, `.psm1`, `.psd1` files, or CI workflow blocks with `shell: pwsh` or `shell: powershell` are created, modified, or reviewed and PowerShell-specific quality controls (error handling, parameter validation, readability, operational safety) must be enforced. Do not use for Bash, generic POSIX `sh`, or language-specific application style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.
10github-codeowners-management
Govern CODEOWNERS rules so review routing reflects real ownership and risk boundaries on GitHub. Use when repository ownership mapping or mandatory reviewer rules must be defined, updated, or audited; do not use for non-GitHub runtime architecture or data-layer design.
9security-authentication
Security workflow for authentication architecture, credential lifecycle, and session/token assurance. Use when login, identity proofing, MFA, or session security decisions are required; do not use for authorization policy design or non-security quality tuning.
9