Automated summary
Guides the user through creating a new CoreWeave GitHub repository with standardized setup, team permissions, and Backstage integration.
Strengths
- Step-by-step interactive process with confirmation before execution
- Automatically configures team permissions, branch protection, and Backstage catalog
- Supports multiple archetypes (blank-repo and go-http-service)
- Integrates with cw CLI and GitHub CLI
Limitations
- Specific to CoreWeave organization
- Requires cw CLI to be installed
- Only two archetypes available
Use this skill when creating a new GitHub repository in the CoreWeave organization that needs standard templates, team permissions, and Backstage integration.
Do not use this skill for repositories outside CoreWeave or when you need custom configurations beyond the provided archetypes.
Security analysis
SafeThe skill instructs users to run CLI commands for creating repositories and managing local config files. It emphasizes getting user confirmation before creating a real repository and only uses allowed Bash operations restricted to repository-related tasks. No destructive, exfiltrating, or obfuscated actions are present.
No concerns found
How this analysis is madeExamples
Create a new CoreWeave GitHub repository for my Go HTTP service named 'order-service' with the go-http-service archetype.Set up a blank GitHub repository called 'project-docs' in CoreWeave for documentation.Walk me through creating a new CoreWeave repository with cw CLI, step by step.name: cw-repo description: Guide through creating a new CoreWeave GitHub repository with proper setup. Use when creating new repos with standardized templates, team permissions, and Backstage integration. allowed-tools:
- Bash(cw repo:*)
- Bash(gh:*)
CW Repository Creation
Guide users through creating new GitHub repositories using the cw CLI. Ensures proper setup with team permissions, branch protection, and Backstage integration.
When to Use This Skill
Use this skill when:
- Creating a new GitHub repository in the CoreWeave organization
- Setting up a new project with proper configuration from the start
- Need a repository with Backstage catalog integration
Instructions
Step 1: Pre-flight Checks
Before starting, verify:
-
CLI installed:
cw version -
Authenticated:
- The command will prompt for GitHub auth if needed
- Uses OAuth device flow
-
Gather requirements:
- Repository name (kebab-case recommended)
- Short description
- Owning team
- Visibility (private/public)
- Archetype (blank-repo or go-http-service)
Step 2: Present Archetype Options
Help the user choose the right archetype:
| Archetype | Best For | |-----------|----------| | blank-repo | General projects, scripts, documentation, non-Go projects | | go-http-service | Go HTTP/gRPC services with CI/CD, Docker, Kubernetes deployment |
Step 3: Guide Through Creation
IMPORTANT: This command creates a real GitHub repository. Always get user confirmation before running.
Show the user what will happen:
cw repo create will:
1. Create GitHub repository: coreweave/<name>
2. Apply archetype template
3. Configure team permissions
4. Set up branch protection (main)
5. Register in Backstage catalog
6. Optionally create a PR for review
Once confirmed, run:
cw repo create
The command is interactive and will prompt for:
- Repository name
- Description
- Team selection
- Visibility
- Archetype selection
Step 4: Post-Creation
After repository creation:
-
Clone the repo:
gh repo clone coreweave/<repo-name> cd <repo-name> -
Verify setup:
- Check branch protection rules
- Verify team access
- Confirm Backstage registration
-
Next steps:
- Add additional components with
/cw-scaffold - Set up local development with
/cw-dev
- Add additional components with
What Gets Created
blank-repo archetype:
.github/CODEOWNERScatalog.yaml(Backstage)- Basic README.md
- Branch protection on main
go-http-service archetype:
- All of blank-repo, plus:
- Go project structure
- Dockerfile
- Kubernetes manifests
- CI/CD workflows
- Makefile
Troubleshooting
Auth issues:
rm -rf ~/.cw/cli/gh.json
cw repo create # Re-authenticates
Permission denied:
- Ensure you have org access
- Check team membership
- Verify GitHub token scopes
Template errors:
rm -rf ~/.cw/cli/cached-templates/
cw repo create # Re-fetches templates
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/coreweave-repository-creation-mmio70t3/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/coreweave-repository-creation-mmio70t3' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/coreweave-repository-creation-mmio70t3/download' --output '.skill-downloads/coreweave-repository-creation-mmio70t3/SKILL.md.part' && mv '.skill-downloads/coreweave-repository-creation-mmio70t3/SKILL.md.part' '.skill-downloads/coreweave-repository-creation-mmio70t3/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/coreweave-repository-creation-mmio70t3/SKILL.md' && test -s '.skill-downloads/coreweave-repository-creation-mmio70t3/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/cw-repo' && cp -R '.skill-downloads/coreweave-repository-creation-mmio70t3' '.claude/skills/cw-repo'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/coreweave-repository-creation-mmio70t3'openskills read 'coreweave-repository-creation-mmio70t3'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/coreweave-repository-creation-mmio70t3/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.