From configure-plugin
Checks and configures Skaffold.yaml in Kubernetes projects for standards compliance, including API version upgrades, port forwarding security fixes, and dotenvx secret hooks.
npx claudepluginhub laurigates/claude-plugins --plugin configure-pluginThis skill is limited to using the following tools:
Check and configure Skaffold against project standards.
Generates design tokens/docs from CSS/Tailwind/styled-components codebases, audits visual consistency across 10 dimensions, detects AI slop in UI.
Records polished WebM UI demo videos of web apps using Playwright with cursor overlay, natural pacing, and three-phase scripting. Activates for demo, walkthrough, screen recording, or tutorial requests.
Delivers idiomatic Kotlin patterns for null safety, immutability, sealed classes, coroutines, Flows, extensions, DSL builders, and Gradle DSL. Use when writing, reviewing, refactoring, or designing Kotlin code.
Check and configure Skaffold against project standards.
| Use this skill when... | Use another approach when... |
|---|---|
| Checking Skaffold configuration compliance for a Kubernetes project | Project has no k8s/ or helm/ directories (Skaffold is not applicable) |
| Fixing port forwarding security issues (binding to 0.0.0.0) | Managing Kubernetes manifests or Helm charts directly |
| Adding dotenvx hooks for secret generation in Skaffold | Configuring container builds without Kubernetes (use /configure:dockerfile) |
| Upgrading Skaffold API version to latest | Debugging Skaffold runtime errors (use system-debugging agent) |
| Creating a standard skaffold.yaml from template | Setting up a non-Skaffold local dev workflow (e.g., Docker Compose) |
find . -maxdepth 1 -type d \( -name 'k8s' -o -name 'helm' \)find . -maxdepth 1 -name \'skaffold.yaml\'grep -m1 apiVersion skaffold.yamlgrep -m1 address skaffold.yamlgrep -m10 'name:' skaffold.yamlfind . -maxdepth 1 -name \'scripts/generate-secrets.sh\'command -v dotenvxfind . -maxdepth 1 -name '.project-standards.yaml' -type fSkills referenced: skaffold-standards, container-development, skaffold-orbstack
Applicability: Only for projects with Kubernetes deployment (k8s/, helm/ directories)
Parse these from $ARGUMENTS:
| Flag | Description |
|---|---|
--check-only | Report status without offering fixes |
--fix | Apply fixes automatically |
CRITICAL: Before configuring Skaffold, verify latest versions:
skaffold/v4beta13Use WebSearch or WebFetch to verify current Skaffold version and API version.
Execute this Skaffold compliance check:
Check for k8s/ or helm/ directories. If neither is found, report "SKIP: Skaffold not applicable (no Kubernetes manifests)" and stop. If found, proceed to check for skaffold.yaml.
Read skaffold.yaml and extract:
Check each setting against these standards:
| Check | Standard | Severity |
|---|---|---|
| API version | skaffold/v4beta13 | WARN if older |
| local.push | false | FAIL if true |
| portForward.address | 127.0.0.1 | FAIL if missing/0.0.0.0 |
| useBuildkit | true | WARN if false |
| kubeContext | orbstack | INFO (recommended for local dev) |
| dotenvx hooks | Build or deploy hooks | INFO (recommended for secrets) |
Security-critical: Port forwarding MUST bind to localhost only (127.0.0.1). Never allow 0.0.0.0 or missing address.
Recommended settings:
db-only or services-only profile for local dev workflowstatusCheck: true with reasonable deadline (180s for init containers)tolerateFailuresUntilDeadline: true for graceful pod initializationPrint a compliance report with:
If --check-only, stop here.
127.0.0.1db-only profile templatescripts/generate-secrets.sh from template in REFERENCE.mdorbstack for local developmentUpdate .project-standards.yaml:
components:
skaffold: "2025.1"
| Context | Command |
|---|---|
| Quick compliance check | /configure:skaffold --check-only |
| Auto-fix all issues | /configure:skaffold --fix |
| Check API version | head -5 skaffold.yaml | grep apiVersion |
| Check port forwarding security | grep -A2 'portForward' skaffold.yaml | grep address |
| List profiles | grep 'name:' skaffold.yaml | grep -v metadata |
Port forwarding without address: 127.0.0.1 exposes services to the network. This is a FAIL condition that should always be fixed.
For the standard Skaffold template, dotenvx integration patterns, and generate-secrets script template, see REFERENCE.md.
/configure:dockerfile - Container configuration/configure:all - Run all compliance checksskaffold-standards skill - Skaffold patterns