Individual skill
coreweave-ci-integration
Unofficial CI integration for CoreWeave deployments using GitHub Actions. Use when automating container builds, deploying inference services from CI, or validating GPU manifests in pull requests. Trigger with phrases like "coreweave CI", "coreweave github actions", "coreweave pipeline", "automate coreweave deploy".
plugins/saas-packs/coreweave-pack/skills/coreweave-ci-integration/SKILL.md
Source commit 0500b275e963c027f6b410e8c49c0446945c574e
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 12, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 2,915
- Repository last updated
- Nov 12, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai Repository topic
- automation Repository topic
- claude-code Repository topic
- devops Repository topic
- mcp Repository topic
- ai-agents Repository topic
- anthropic Repository topic
- claude-code-plugins Repository topic
- developer-tools Repository topic
- llm Repository topic
- saas Declared skill tag
- gpu-cloud Declared skill tag
- kubernetes Declared skill tag
- inference Declared skill tag
- coreweave Declared skill tag
- devops Derived category
- devops-containers Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 9,092 bytesSKILL.mdcore · 9,092 bytesSKILL.mdcore · 9,092 bytesSKILL.mdcore · 9,092 bytesSKILL.mdcore · 9,092 bytesdocs/BLUEPRINT.mddoc · 9,028 byteseval-spec.yamlasset · 8,836 bytesreferences/cost-gate.mddoc · 3,934 bytesreferences/evidence-contract.mddoc · 1,932 bytesreferences/operator-notes.mddoc · 1,229 bytesscripts/review-cost-plan.pyruns · 7,437 bytesscripts/review-workflow.pyruns · 3,277 bytesscripts/review_common.pyruns · 3,538 bytestests/fixtures/cases.jsonasset · 8,735 bytestests/fixtures/example.jsonasset · 825 bytes
Read excerpt
# UNOFFICIAL CI INTEGRATION FOR COREWEAVE
> **Community-contributed.** Not affiliated with, endorsed by, or sponsored by CoreWeave, Inc. CoreWeave is a registered trademark of CoreWeave, Inc.
## Overview
Separate credential-free pull-request tests from an approved, post-merge staging deployment.
Use Read to inspect the workflow and locked project dependencies, Write the proposed workflow, and Edit it only after the repository owner reviews its trust boundaries.
The example assumes an npm project with `package-lock.json`, `npm test`, and a reviewed `k8s/staging.yaml`; adapt these to the actual repository.
## Prerequisites
- A protected main branch and a protected `coreweave-staging` environment with required reviewers.
- Environment variables `CW_CONTEXT`, `CW_NAMESPACE`, `CW_DEPLOYMENT` and a reviewed staging manifest targeting that exact namespace.
- A dedicated, least-privilege kubeconfig stored as environment secret `COREWEAVE_KUBECONFIG_B64`.