Index of every page on this site: llms.txt
All skills
jeremylongshore avatar

/coreweave-install-auth

@820dfc8
Run it yourself

Configure CoreWeave Kubernetes Service (CKS) access with kubeconfig and API tokens. Use when setting up kubectl access to CoreWeave, configuring CKS clusters, or authenticating with CoreWeave cloud services. Trigger with phrases like "install coreweave", "setup coreweave", "coreweave kubeconfig", "coreweave auth", "connect to coreweave".

Use this Skill: https://skilld.dev/gh/jeremylongshore/tons-of-skills-marketplace/coreweave-install-auth

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈91 tokens for metadata: the name and description. ≈1.1k when used: this file. ≈2.5k more on demand in 2 files.

Description uses 4.5% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈364 characters, or 4.5%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

CoreWeave Access and identity verification

Community-contributed. Not affiliated with, endorsed by, or sponsored by CoreWeave, Inc. CoreWeave is a registered trademark of CoreWeave, Inc.

Overview

Verify an approved CKS kubeconfig and namespace before any workload operation. Use Read to inspect the approved input files, Write the evidence report, and Edit only the proposed local artifact before review. These procedures complement CoreWeave’s official skills; they do not redistribute or replace that upstream distribution.

Prerequisites

  • The owner-approved organization, cluster context, namespace and resource names.
  • A trusted kubeconfig from the approved secret location; no raw credentials in source, logs or terminal history.
  • Installed kubectl compatible with the cluster, and authority for each proposed read or change.
  • An agreed success criterion, resource budget, evidence destination and recovery owner.

Instructions

  1. Obtain the cluster-specific kubeconfig through the Cloud Console and current Managed Auth instructions. Treat the entire file as a secret; it embeds a token. Store it in the approved private credential location, not .env, Git or a support bundle.

  2. Read the intended organization, cluster, context, namespace and token expiry from the access request. Review any exec-based credential plugin in an externally supplied kubeconfig before using it.

  3. Check namespace read permission and record the result. A successful client-version command does not prove server connectivity. Distinguish authentication failure from Kubernetes authorization denial.

  4. If access to Nodes is approved, inspect current instance-type labels and allocatable GPUs. A denied Node listing does not mean the organization has no GPUs.

  5. For Mission Control MCP, use the official configuration guide and discover read-only tools. Do not infer that an API token and a Kubernetes service-account token are interchangeable.

Examples

Set CW_CONTEXT and CW_NAMESPACE from the approved access request. Set each referenced resource variable to the exact owner-selected resource, not a wildcard or the first matching Pod.

: "${CW_CONTEXT:?approved context required}" "${CW_NAMESPACE:?approved namespace required}"
kubectl --context="$CW_CONTEXT" --namespace="$CW_NAMESPACE" auth can-i get pods
kubectl --context="$CW_CONTEXT" --namespace="$CW_NAMESPACE" get pods --request-timeout=20s
# Only with approved cluster-level read access:
kubectl --context="$CW_CONTEXT" get nodes -L node.kubernetes.io/instance-type --request-timeout=20s

These are operator examples, not commands run by this package’s offline tests. Mutating examples require approval for the exact manifest, environment and budget before execution.

Output

  • A UTC-stamped review identifying the observed state, evidence coverage and unresolved assumptions.
  • A specific proposed next step, the owner who can authorize it, and a measurable acceptance or recovery check.
  • A clear incomplete result when credentials, capacity, metrics or live validation are unavailable.

Error Handling

Condition Response
Authentication or authorization denied Stop; verify the intended identity and scope without escalating permissions automatically.
Empty or stale evidence Record unknown and collect a bounded fresh sample; never substitute zero or healthy.
Admission, rollout or acceptance failure Preserve the sanitized error and use the reviewed recovery path with its owner.
Output may contain a secret or workload data Restrict sharing and review/redact before retaining or uploading it.

Resources

Evidence status

Source-reviewed guidance with offline repository checks. No live CoreWeave account, paid GPU workload or provider-backed behavioral evaluation was used to validate this guide. Record live results separately before claiming workload success.

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts2mo3 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    The skill provides legitimate instructions for setting up and authenticating with the CoreWeave Kubernetes Service (CKS). It follows security best practices by using placeholders for credentials and recommending the use of environment files for secret management.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

Signed by skilld at 820dfc8. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 20 hours ago.

Activeupdated last week
What it can do
Reads files Edits files Runs commands
version
1.15.0
author
Jeremy Longshore <jeremy@intentsolutions.io>
tags
[
  "saas",
  "gpu-cloud",
  "kubernetes",
  "inference",
  "coreweave"
]
All 5 allowed tools
ReadWriteEditBash(kubectl:*)Grep
Other metadata
compatibility
Designed for Claude Code

README badge

README badge for jeremylongshore/tons-of-skills-marketplace/coreweave-install-auth