Agent skill · software engineering · jeremylongshore
coreweave-multi-env-setup
Configure CoreWeave across development, staging, and production environments.
Why this skill is useful
Adds executable scripts and specific Kubernetes commands for managing CoreWeave GPU environments that aren't in public documentation.
What it needs
Requires kubectl, kustomize installed locally. Requires coreweave account access. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
CoreWeave Multi-Environment Setup Community-contributed. Not affiliated with, endorsed by, or sponsored by CoreWeave, Inc. CoreWeave is a registered trademark of CoreWeave, Inc. Overview CoreWeave GPU cloud requires strict environment separation to control infrastructure costs and prevent resource contention. Each environment maps to an isolated Kubernetes namespace with its own GPU quota, scaling policy, and access controls. Development uses cheaper GPU tiers for iteration speed, staging mirrors production GPU types for accurate benchmarking, and production runs full-scale with no scale-to-zero to guarantee inference latency SLAs. Environment Configuration Prerequisites Separate, approved namespaces and service identities for development, staging, and production. Environment-specific secrets injected by a secrets manager, never committed .env files. A promotion owner, staging evaluation gate, and production rollback manifest. Instructions 1. Define overlays that differ only in reviewed capacity, endpoint, and namespace values. 2. Validate required variables and secret references before applying an overlay. 3. Promote dev to staging, run the service evaluation, then use a controlled production rollout. 4. Roll back the production overlay on an SLO, quality, or security-gate failure; do not copy staging credentials into production. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/coreweave-multi-env-setup--e286de