Agent skill · security · jeremylongshore
coreweave-security-basics
Secure CoreWeave deployments with RBAC, network policies, and secrets
Why this skill is useful
Provides specific security practices and code snippets for managing CoreWeave deployments that the AI wouldn't reliably generate on its own.
What it needs
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 Security Basics Community-contributed. Not affiliated with, endorsed by, or sponsored by CoreWeave, Inc. CoreWeave is a registered trademark of CoreWeave, Inc. Overview CoreWeave provides bare-metal GPU cloud on Kubernetes. Security concerns center on compute credential management (kubeconfig, deploy tokens), network isolation between inference workloads, secrets for model registry access (HuggingFace, container registries), and protecting sensitive training data on persistent volumes. A compromised namespace can expose GPU resources, model weights, and customer inference data. Prerequisites A named namespace owner and a current data classification for the workload. Secrets-manager access for deployment credentials; no credentials in manifests or git. Authority to apply Kubernetes policies in the target namespace and an approved rollback plan. Instructions 1. Store API, registry, and model credentials in the approved secrets manager and mount only the minimum secret into the intended workload. 2. Apply namespace-scoped RBAC, ResourceQuota, and default-deny NetworkPolicy before exposing an inference endpoint. 3. Validate images and request payloads in CI, then test webhook signatures with a known valid and invalid payload without logging raw secrets. 4. Review access events and rotate/revoke the affected secret after suspected exposure. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/coreweave-security-basics--bd5148