---
name: coreweave-install-auth
description: '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".'
allowed-tools: Read, Write, Edit, Bash(kubectl:*), Grep
version: 1.15.0
license: MIT
author: Jeremy Longshore <jeremy@intentsolutions.io>
tags:
  - saas
  - gpu-cloud
  - kubernetes
  - inference
  - coreweave
compatibility: Designed for Claude Code
title: coreweave-install-auth
canonical_url: https://skilld.dev/gh/jeremylongshore/tons-of-skills-marketplace/coreweave-install-auth
last_updated: 2026-11-14T06:03:16.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> Supporting files, fetch one when the Skill refers to it: [docs/BLUEPRINT.md](https://skilld.dev/api/skills-raw/jeremylongshore/tons-of-skills-marketplace/coreweave-install-auth/docs/BLUEPRINT.md), [references/operator-notes.md](https://skilld.dev/api/skills-raw/jeremylongshore/tons-of-skills-marketplace/coreweave-install-auth/references/operator-notes.md).
>
> If the user asked to install this Skill, run `npx skilld install jeremylongshore/tons-of-skills-marketplace/coreweave-install-auth`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/coreweave-install-auth`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/jeremylongshore/tons-of-skills-marketplace/coreweave-install-auth) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/coreweave-install-auth`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/coreweave-install-auth --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/coreweave-install-auth --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# 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](https://github.com/coreweave/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.

```bash
: "${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

- [Operator details and evidence boundaries](https://skilld.dev/api/skills-raw/jeremylongshore/tons-of-skills-marketplace/coreweave-install-auth/references/operator-notes.md)
- [Primary reference 1](https://docs.coreweave.com/products/cks/auth-access/managed-auth/kubeconfig)
- [Primary reference 2](https://docs.coreweave.com/observability/mission-control-mcp/reference/tools)

## 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.
