Install the "crosvm-testing" agent skill from https://github.com/google/crosvm/tree/main/.agents/skills/crosvm_testing into .claude/skills/crosvm-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "crosvm-testing", then confirm the skill loads.
Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
skills CLI
$ npx skills add google/crosvm --skill crosvm-testing -a codex
Project install goes to .agents/skills/; add -g for ~/.codex/skills/.
Install the "crosvm-testing" agent skill from https://github.com/google/crosvm/tree/main/.agents/skills/crosvm_testing into .agents/skills/crosvm-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "crosvm-testing", then confirm the skill loads.
Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
skills CLI
$ npx skills add google/crosvm --skill crosvm-testing -a cursor
Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.
Install the "crosvm-testing" agent skill from https://github.com/google/crosvm/tree/main/.agents/skills/crosvm_testing into .cursor/skills/crosvm-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "crosvm-testing", then confirm the skill loads.
Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
skills CLI
$ npx skills add google/crosvm --skill crosvm-testing -a gemini-cli
Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.
Install the "crosvm-testing" agent skill from https://github.com/google/crosvm/tree/main/.agents/skills/crosvm_testing into .gemini/skills/crosvm-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "crosvm-testing", then confirm the skill loads.
Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
GitHub CLI
$ gh skill install google/crosvm crosvm-testing
Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
skills CLI
$ npx skills add google/crosvm --skill crosvm-testing -a github-copilot
Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.
Install the "crosvm-testing" agent skill from https://github.com/google/crosvm/tree/main/.agents/skills/crosvm_testing into .github/skills/crosvm-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "crosvm-testing", then confirm the skill loads.
GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
skills CLI
$ npx skills add google/crosvm --skill crosvm-testing -a opencode
OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
Install the "crosvm-testing" agent skill from https://github.com/google/crosvm/tree/main/.agents/skills/crosvm_testing into .opencode/skills/crosvm-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "crosvm-testing", then confirm the skill loads.
OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
Skill name
crosvm-testing
GitHub stars
1.3k
Token cost
~847 tokens
SKILL.md length
344 words
Files
1
Skills in repo
4
Repo updated
First seen
Licence
BSD-3-Clause
At a glance
Skill to assist with running tests and managing test VMs in the crosvm repository.
Works in 4 steps: Unit Tests → Integration Tests → Test Filtering → …
Tasks that involve Integration testing
SKILL.md covers Running Tests (tools/run_tests) and Managing Test VMs…
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Crosvm Testing is an agent skill from google/crosvm, published by the product's own GitHub organization. Skill to assist with running tests and managing test VMs in the crosvm repository.
Its SKILL.md is about 850 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Testing & QA, covering Integration testing and Unit testing. The repository describes itself as: The Chrome OS Virtual Machine Monitor - Mirror of https://chromium.googlesource.com/crosvm/crosvm/. The licence is BSD-3-Clause.
When your agent uses it
Tasks that involve Integration testing
Tasks that involve Unit testing
Example prompts
“/crosvm-testing”
Workflow steps
4 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 2c8433b. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
nexte.st
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Crosvm Testing loads about 847 tokens when it runs. Until then it costs about 24 tokens; SKILL.md has 344 words of instructions outside code blocks.
Always· name and description, kept in context so the agent knows when to use it
~24
When it runs· the whole SKILL.md, loaded when a task matches
~847
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
Download SKILL.mdSave it as .claude/skills/crosvm-testing/SKILL.md (or your agent's skills folder).
name
crosvm-testing
description
Skill to assist with running tests and managing test VMs in the crosvm repository.
Crosvm Testing (tools/run_tests & tools/testvm)
This skill covers running the crosvm test suite and managing the virtual machines used for
integration testing.
[!TIP] When you have completed your code changes and are ready to commit or upload, please run the
overall presubmit checks according to the crosvm-contribution-workflow
SKILL.md.
Running Tests (tools/run_tests)
The tools/run_tests script is the primary test runner. It supports unit tests (running on the host
or via emulators) and integration tests (running on a test VM or the host).
1. Unit Tests
Run host native unit tests:bash
./tools/run_tests
Run unit tests for a specific platform (via emulator):bash
./tools/run_tests -p <platform>
Supported platforms: x86_64, aarch64, armhw, mingw64, riscv64. Example for ARM64:
./tools/run_tests -p aarch64Example for Windows (via Wine): ./tools/run_tests -p mingw64
2. Integration Tests
Integration tests require a Device Under Test (DUT).
Run integration tests on a Test VM (Recommended):bash
./tools/run_tests --dut=vm
This will automatically start a test VM, run the tests inside it, and keep the VM running for
subsequent runs.
Run integration tests on the Host:bash
./tools/run_tests --dut=host
Note: This may not work on all host configurations and might require root.
3. Test Filtering
The runner supports nextest filter expressions using the -E or --filter-expr flag. See
nextest documentation for details.
--no-unit-tests: Skip unit tests and only run integration tests.
--no-integration-tests: Skip integration tests.
--run-root-tests: Enable integration tests that require root privileges.
--retries <N>: Retry failed tests N times.
--repetitions <N>: Repeat all tests N times (useful for detecting flakiness).
Managing Test VMs (tools/testvm, tools/x86vm, tools/aarch64vm)
For integration testing (--dut=vm), crosvm uses test VMs. You can manage these VMs using
tools/x86vm (for x86_64) or tools/aarch64vm (for ARM64). These are wrappers around
tools/testvm.
Replace x86vm with aarch64vm in the commands below depending on the architecture you are
testing.
Start the VM:bash
./tools/x86vm up
Open an interactive SSH shell into the VM:bash
./tools/x86vm shell
(This will start the VM if it is not already running).
Crosvm Testing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
Tests JavaScript embedded in an HTML file in two layers: pytest checks of the logic ported to Python, and Playwright runs in a real browser for the DOM.
A skill your agent uses when the user says 'write tests', 'add tests', 'test coverage', 'unit tests', 'integration tests', 'component tests', 'mocking', 'edge cases', or needs to generate tests with…
Skill to assist with running tests and managing test VMs in the crosvm repository. Crosvm Testing is an agent skill from google/crosvm, published by the product's own GitHub organization. Skill to assist with running tests and managing test VMs in the crosvm repository.
When should I use Crosvm Testing?
Crosvm Testing fits situations like: tasks that involve Integration testing; tasks that involve Unit testing.
How do I install Crosvm Testing in Claude Code?
Run `npx skills add google/crosvm --skill crosvm-testing -a claude-code`. Or copy the skill folder (.agents/skills/crosvm_testing in google/crosvm) into .claude/skills/crosvm-testing in your project. Claude Code loads it when a task matches its description.
How do I install Crosvm Testing in Codex?
Run `npx skills add google/crosvm --skill crosvm-testing -a codex`. Or copy the skill folder (.agents/skills/crosvm_testing in google/crosvm) into .agents/skills/crosvm-testing in your project. Codex loads it when a task matches its description.
Can I use Crosvm Testing in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add google/crosvm --skill crosvm-testing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/crosvm-testing, .gemini/skills/crosvm-testing, .github/skills/crosvm-testing and .opencode/skills/crosvm-testing in your project.
What does Crosvm Testing need to run?
SKILL.md names no scripts, command-line tools or credentials: Crosvm Testing is instructions for the agent only.
Does Crosvm Testing access the network?
SKILL.md names 1 domain. As links in the text: nexte.st. This is read from the text; nothing was executed.
Is Crosvm Testing safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Crosvm Testing use?
Crosvm Testing is published under the BSD-3-Clause licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Crosvm Testing use?
About 847 tokens (SKILL.md is roughly 3.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Crosvm Testing?
Skills that share tags, products or a category with Crosvm Testing: JS-in-HTML Testing (liaohch3/claude-tap, 3.3k stars), Add Acceptance Test (talkincode/toughradius, 691 stars), Testing (celeriant/celeriant-db, 114 stars) and Testing Patterns (langchain-ai/skills-benchmarks, 118 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Crosvm Testing?
google (a GitHub organization, an official publisher) maintains it in google/crosvm, which has 1,329 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on October 7, 2026.
Source: google/crosvm on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.
