Install the "crosvm-contribution-workflow" agent skill from https://github.com/google/crosvm/tree/main/.agents/skills/crosvm_contribution_workflow into .claude/skills/crosvm-contribution-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "crosvm-contribution-workflow", 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-contribution-workflow -a codex
Project install goes to .agents/skills/; add -g for ~/.codex/skills/.
Install the "crosvm-contribution-workflow" agent skill from https://github.com/google/crosvm/tree/main/.agents/skills/crosvm_contribution_workflow into .agents/skills/crosvm-contribution-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "crosvm-contribution-workflow", 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-contribution-workflow -a cursor
Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.
Install the "crosvm-contribution-workflow" agent skill from https://github.com/google/crosvm/tree/main/.agents/skills/crosvm_contribution_workflow into .cursor/skills/crosvm-contribution-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "crosvm-contribution-workflow", 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-contribution-workflow -a gemini-cli
Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.
Install the "crosvm-contribution-workflow" agent skill from https://github.com/google/crosvm/tree/main/.agents/skills/crosvm_contribution_workflow into .gemini/skills/crosvm-contribution-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "crosvm-contribution-workflow", 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.
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-contribution-workflow -a github-copilot
Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.
Install the "crosvm-contribution-workflow" agent skill from https://github.com/google/crosvm/tree/main/.agents/skills/crosvm_contribution_workflow into .github/skills/crosvm-contribution-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "crosvm-contribution-workflow", 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-contribution-workflow -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-contribution-workflow" agent skill from https://github.com/google/crosvm/tree/main/.agents/skills/crosvm_contribution_workflow into .opencode/skills/crosvm-contribution-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "crosvm-contribution-workflow", 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-contribution-workflow
GitHub stars
1.3k
Token cost
~1.5k tokens
SKILL.md length
693 words
Files
1
Skills in repo
4
Repo updated
First seen
Licence
BSD-3-Clause
At a glance
Skill to assist with the contribution workflow for crosvm. An agent skill from google/crosvm.
Works in 2 steps: Auto-formatting → Running Checks
Run presubmit checks before committing
SKILL.md covers Formatting and Presubmit Checks, Uploading Changes, Commit Message Guidelines and End-to-End Contribution Journey
Calls git
What it does
Crosvm Contribution Workflow is an agent skill from google/crosvm, published by the product's own GitHub organization. Skill to assist with the contribution workflow for crosvm. ALL agents making code changes MUST use this skill to run presubmit checks before committing.
Its SKILL.md is about 1.5k 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 Development. 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
Run presubmit checks before committing
Example prompts
“/crosvm-contribution-workflow”
Workflow steps
2 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
Shell commands in SKILL.md call:
git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
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 Contribution Workflow loads about 1.5k tokens when it runs. Until then it costs about 45 tokens; SKILL.md has 693 words of instructions outside code blocks.
Always· name and description, kept in context so the agent knows when to use it
~45
When it runs· the whole SKILL.md, loaded when a task matches
~1.5k
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-contribution-workflow/SKILL.md (or your agent's skills folder).
name
crosvm-contribution-workflow
description
Skill to assist with the contribution workflow for crosvm. ALL agents making code changes MUST use this skill to run presubmit checks before committing.
Contribution Workflow Skill
This skill assists with the crosvm contribution workflow. ALL agents making code changes MUST use
this skill to verify their changes (by compiling and running tests) before proceeding to commit or
requesting review, even if the user does not explicitly ask to run tests.
Formatting and Presubmit Checks
All commands must be executed from the repository root directory.
Choosing the Right Test Method
Depending on the scope of your changes, choose the appropriate method to verify your work. The
relevant checks must pass before you proceed to create a commit or request review.
./tools/dev_container cargo check
Usage: Use this during normal development iterations.
Description: It attempts to compile the project with the default feature set. Fast and
useful for quick feedback on syntax and basic type checking.
tools/dev_container ./tools/presubmit quick
Usage: Run this as a minimum sanity check before creating a commit.
Description: Performs a health check, runs unit tests on x86, and runs clippy lints.
tools/dev_container ./tools/presubmit
Usage: Run this when you have made changes that might affect multiple platforms or are more
substantial.
Description: In addition to the quick checks, this performs cross-compilation and runs unit
tests for other targets. Note: The default set does not cover all platforms (e.g., riscv).
tools/dev_container ./tools/presubmit clippy
Usage: Run this to quickly check all platforms (including riscv) for cross-platform changes.
Description: Runs clippy lints for all supported platforms. This is a relatively quick way
to ensure your changes don't break compilation on any platform.
tools/dev_container ./tools/presubmit all
Usage: Run this before final submission or for complex changes that require full validation.
Description: This is the most thorough check. It runs all the above tests on all supported
platforms, including end-to-end (e2e) tests using QEMU. Note: This takes a significant amount
of time.
Commands
1. Auto-formatting
Automatically fixes code formatting. This also applies to Markdown files (.md) in addition to
source code.
bash
tools/dev_container ./tools/fmt
2. Running Checks
Use one of the methods described above. Example for quick check:
bash
tools/dev_container ./tools/presubmit quick
[!TIP] If your tests fail on presubmit and you need to debug the tests individually or inspect the
VM environment, please refer to the crosvm-testing SKILL.md.
Uploading Changes
Once your changes are verified and formatted, you can upload them to Gerrit for review.
We use a custom tool ./tools/cl for this. The basic command to upload is:
bash
./tools/cl upload
[!TIP] For advanced usage of the CL tool, including rebasing downstream branches, checking CL
status, and pruning old branches, see the specialized crosvm-cl-tool
SKILL.md.
Commit Message Guidelines
Refer to these guidelines when writing commit messages for crosvm. You must only write a commit
message AFTER ensuring all necessary tests pass.
Show full SKILL.md (279 more words)Show less
1. Subject Line
Format: Starts with a tag representing the component, followed by a colon and space, then the
description.
Example: devices: vhost: user: Add Connection type
Tags: Usually the name of the crate modified (e.g., devices:, base:). Use paths for
specific components (e.g., devices: vhost: user:).
Length: No more than 50 characters, including tags.
2. Body
Content: State the motivation followed by the impact/action.
Wrapping: Text must be wrapped to 72 characters.
3. BUG Lines
Format: BUG=b:<bug number> for Google issue tracker, or BUG=None.
You can have multiple BUG lines.
Tip: If you do not know the bug number, ask the user for clarification.
4. TEST Lines
Format: Describe how the change was tested in free form.
You can have multiple TEST lines.
5. Change-Id
The gerrit commit message hook will insert this automatically if the commit-msg hook is installed.
Important: The Change-Id links the commit to a specific Gerrit change list (CL). Unless
explicitly requested by the user, DO NOT change or remove the Change-Id when cherry-picking,
rebasing, or amending commits.
Example Commit Message
devices: vhost: user: vmm: Add Connection type
This abstracts away the cross-platform differences:
cfg(any(target_os = "android", target_os = "linux")) uses a Unix
domain domain stream socket to connect to the vhost-user backend, and
cfg(windows) uses a Tube.
BUG=b:249361790
TEST=tools/presubmit all
Change-Id: I47651060c2ce3a7e9f850b7ed9af8bd035f82de6
End-to-End Contribution Journey
Here is the typical sequence of steps for contributing a change:
Crosvm Contribution Workflow 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.
Crosvm Contribution Workflow compared with similar skills
Skill
Stars
Used in
Tokens
Auto-check
Licence
Repo updated
Crosvm Contribution Workflow this skillgoogle/crosvm
Captures screenshots of the running Mailspring dev app for docs, PRs or visual checks by launching it with a debugging port, driving the UI and clipping to an element.
Triages and lands a batch of open Dependabot PRs in the Onyx repo, where main is gated exclusively by GitHub's merge queue: approves and enqueues green PRs, closes superseded duplicates, fixes…
Analyze an Android pull request, branch, commit, or patch for user-visible changes and produce reproducible before/after screenshots from isolated builds.
Records a project's quality bar in CONSTRAINTS.md and watches diffs for signs an agent quietly weakened it, such as suppressions, skipped tests or lowered thresholds.
This skill should be used when the user is writing Go code and needs guidance on Go-specific pedantry: error wrapping with fmt.Errorf and %w, interface design (accept interfaces return structs)…
Skill to assist with the contribution workflow for crosvm. An agent skill from google/crosvm. Crosvm Contribution Workflow is an agent skill from google/crosvm, published by the product's own GitHub organization. Skill to assist with the contribution workflow for crosvm.
When should I use Crosvm Contribution Workflow?
Crosvm Contribution Workflow fits situations like: run presubmit checks before committing.
How do I install Crosvm Contribution Workflow in Claude Code?
Run `npx skills add google/crosvm --skill crosvm-contribution-workflow -a claude-code`. Or copy the skill folder (.agents/skills/crosvm_contribution_workflow in google/crosvm) into .claude/skills/crosvm-contribution-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Crosvm Contribution Workflow in Codex?
Run `npx skills add google/crosvm --skill crosvm-contribution-workflow -a codex`. Or copy the skill folder (.agents/skills/crosvm_contribution_workflow in google/crosvm) into .agents/skills/crosvm-contribution-workflow in your project. Codex loads it when a task matches its description.
Can I use Crosvm Contribution Workflow 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-contribution-workflow -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-contribution-workflow, .gemini/skills/crosvm-contribution-workflow, .github/skills/crosvm-contribution-workflow and .opencode/skills/crosvm-contribution-workflow in your project.
What does Crosvm Contribution Workflow need to run?
Going by SKILL.md and its folder, Crosvm Contribution Workflow needs the command-line tools its instructions call (git).
Does Crosvm Contribution Workflow access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Crosvm Contribution Workflow 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 Contribution Workflow use?
Crosvm Contribution Workflow 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 Contribution Workflow use?
About 1.5k tokens (SKILL.md is roughly 6k 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 Contribution Workflow?
Skills that share tags, products or a category with Crosvm Contribution Workflow: PR Babysitter (openinterpreter/openinterpreter, 69k stars), Mailspring App Screenshots (Foundry376/Mailspring, 18k stars), Merge Dependabot PRs (onyx-dot-app/onyx, 32k stars) and Android UI Visual Review (permissionlesstech/bitchat-android, 7.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Crosvm Contribution Workflow?
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.
