rwx — Claude Code skill: what it does, how to install
Helps configure RWX CI/CD pipelines, execute test runs in sandboxes, and inspect build failures from the terminal.
npx skills add rwx-cloud/skills --skill rwx -a claude-codeWhat rwx does
The skill guides your coding agent when creating or updating workflow definitions in the .rwx directory. It pulls reference schemas using rwx docs pull and validates configurations with rwx lint .rwx/<name>.yml before execution.
You do not need to commit or push your branch to run a test pipeline. The rwx run .rwx/<file>.yml --wait command automatically patches the remote clone with your uncommitted local files. Isolated commands execute via rwx sandbox exec.
Without an installed RWX CLI and an active login via rwx whoami, this skill will fail immediately. It relies entirely on local CLI authentication.
What it helps with
- draft and validate CI/CD definitions in the
.rwxdirectory - execute remote test runs using uncommitted local changes
- debug build failures and inspect run logs directly in terminal
- run custom commands inside an RWX sandbox environment
Example prompts for the agent
- Check why the CI run failed on this branch
- Generate a pipeline config in
.rwx/ci.ymland run lint on it - Execute
npm testinside an RWX sandbox
How to install rwx
1Skills CLI (Vercel)
npx skills add rwx-cloud/skills --skill rwx -a claude-code2Manually: put the files in place
~/.claude/skills/rwx/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/rwx/
1Skills CLI (Vercel)
npx skills add rwx-cloud/skills --skill rwx -a codex2Manually: put the files in place
.agents/skills/rwx/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add rwx-cloud/skills --skill rwx -a cursor2Manually: put the files in place
.cursor/skills/rwx/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install rwx-cloud/skills rwx2Manually: put the files in place
.github/skills/rwx/SKILL.md1Skills CLI (Vercel)
npx skills add rwx-cloud/skills --skill rwx -a gemini-cli2Platform CLI
gemini skills install https://github.com/rwx-cloud/skills --path plugins/rwx/skills/rwxManually: put the files in place
.devin/skills/rwx/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add rwx-cloud/skills --skill rwx -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about rwx
How to install rwx in Claude Code?
Run npx skills add rwx-cloud/skills --skill rwx -a claude-code. The skill file will be created at ~/.claude/skills/rwx/SKILL.md.
What does the rwx skill do?
It gives your agent instructions for RWX CLI commands. The agent can search documentation, trigger runs, inspect failing jobs, and launch sandboxes.
Do I need to push git commits before starting an RWX run?
Pushing is not required. RWX automatically syncs and applies your local workspace diffs onto the runner repository.
Source text
SKILL.md · MIT
---
name: rwx
metadata:
version: "0.2.0"
description: >-
Used to create, modify, or understand an RWX CI/CD config or any other file in
a `.rwx` directory. TRIGGER when: the user asks about RWX; wants to create or
modify an RWX config; says things like "CI failed", "CI is red", or "tests are
failing in CI"; asks "what's failing on my PR / branch / commit?"; wants to
run tests or build steps in a sandbox; wants to debug test failures, check a
run status, fetch logs/artifacts, or start a run loop.
argument-hint: [optional description, e.g. "CI pipeline with tests and deploy"]
allowed-tools:
Bash(rwx lint *), Bash(rwx docs *), Bash(rwx logs *), Bash(rwx artifacts *),
Bash(rwx results *), Bash(rwx whoami), Bash(rwx * --help)
---
# Using RWX
Ensure the user is signed in and on the latest version of the RWX CLI before
getting started: `rwx whoami`
## RWX Run Definition Syntax
When working with RWX, it is extremely important to use the reference
documentation. Run the following command to pull the reference documentation.
The output is already constrained in size, and it is very important to not
truncate the output of this command.
`rwx docs pull /migrating/rwx-reference`
If you encounter a question not covered by these references, use
`rwx docs search "<query>"` to find the relevant documentation page, then
`rwx docs pull` the result.
## Executing Runs
If the user chooses, you can kick off an actual run on RWX:
`rwx run .rwx/<file>.yml --wait`
When the run finishes, results will be shown, and you can iterate until the run
passes.
You do not need to commit or push to invoke a run with RWX, even if the run
definition references a commit sha. RWX will automatically patch the git clone
with the local contents.
## Check CI / run results or status of a branch
If you have been asked to check on run failures or CI failures, or if you have
been asked to check the current run status of the current branch or a given
branch:
`rwx results -h`
## Sandboxes
If the user mentions using a sandbox:
`rwx sandbox exec -- <command>`
## Generate or Modify RWX Config
You may have been tasked with creating, modifying, or understanding/explaining
an RWX CI/CD config for this project. Use the same aforementioned documentation.
When making changes, you can run validation on the config:
rwx lint .rwx/<name>.yml
© rwx-cloud · MIT · rwx-cloud/skills
