Agent skill

Physical Chromebook Debugging

Build and deploy Chrome to a physical ChromeOS device, monitor logs, and take screenshots over SSH.

BSD-3-ClauseAuto-check passedDevelopment

Install Physical Chromebook Debugging

skills CLI

$ npx skills add nwjs/chromium.src --skill physical-chromebook-debugging -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install nwjs/chromium.src physical-chromebook-debugging --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/nwjs/chromium.src.git skills-src && mkdir -p .claude/skills && cp -r skills-src/agents/skills/physical-chromebook-debugging .claude/skills/physical-chromebook-debugging && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "physical-chromebook-debugging" agent skill from https://github.com/nwjs/chromium.src/tree/main/agents/skills/physical-chromebook-debugging into .claude/skills/physical-chromebook-debugging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "physical-chromebook-debugging", 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.

$skill-installer

$skill-installer install https://github.com/nwjs/chromium.src/tree/main/agents/skills/physical-chromebook-debugging

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 nwjs/chromium.src --skill physical-chromebook-debugging -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install nwjs/chromium.src physical-chromebook-debugging --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/nwjs/chromium.src.git skills-src && mkdir -p .agents/skills && cp -r skills-src/agents/skills/physical-chromebook-debugging .agents/skills/physical-chromebook-debugging && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "physical-chromebook-debugging" agent skill from https://github.com/nwjs/chromium.src/tree/main/agents/skills/physical-chromebook-debugging into .agents/skills/physical-chromebook-debugging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "physical-chromebook-debugging", 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 nwjs/chromium.src --skill physical-chromebook-debugging -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install nwjs/chromium.src physical-chromebook-debugging --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/nwjs/chromium.src.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/agents/skills/physical-chromebook-debugging .cursor/skills/physical-chromebook-debugging && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "physical-chromebook-debugging" agent skill from https://github.com/nwjs/chromium.src/tree/main/agents/skills/physical-chromebook-debugging into .cursor/skills/physical-chromebook-debugging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "physical-chromebook-debugging", 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.

gemini skills install

$ gemini skills install https://github.com/nwjs/chromium.src.git --path agents/skills/physical-chromebook-debugging

--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 nwjs/chromium.src --skill physical-chromebook-debugging -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install nwjs/chromium.src physical-chromebook-debugging --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/nwjs/chromium.src.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/agents/skills/physical-chromebook-debugging .gemini/skills/physical-chromebook-debugging && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "physical-chromebook-debugging" agent skill from https://github.com/nwjs/chromium.src/tree/main/agents/skills/physical-chromebook-debugging into .gemini/skills/physical-chromebook-debugging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "physical-chromebook-debugging", 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 nwjs/chromium.src physical-chromebook-debugging

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 nwjs/chromium.src --skill physical-chromebook-debugging -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/nwjs/chromium.src.git skills-src && mkdir -p .github/skills && cp -r skills-src/agents/skills/physical-chromebook-debugging .github/skills/physical-chromebook-debugging && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "physical-chromebook-debugging" agent skill from https://github.com/nwjs/chromium.src/tree/main/agents/skills/physical-chromebook-debugging into .github/skills/physical-chromebook-debugging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "physical-chromebook-debugging", 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 nwjs/chromium.src --skill physical-chromebook-debugging -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install nwjs/chromium.src physical-chromebook-debugging --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/nwjs/chromium.src.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/agents/skills/physical-chromebook-debugging .opencode/skills/physical-chromebook-debugging && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "physical-chromebook-debugging" agent skill from https://github.com/nwjs/chromium.src/tree/main/agents/skills/physical-chromebook-debugging into .opencode/skills/physical-chromebook-debugging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "physical-chromebook-debugging", 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: physical-chromebook-debugging
GitHub stars: 160
Token cost: ~464 tokens
SKILL.md length: 123 words
Files: 4
Skills in repo: 64
Repo updated: Oct 3, 2026
First seen: Oct 8, 2026
Licence: BSD-3-Clause

At a glance

Build and deploy Chrome to a physical ChromeOS device, monitor logs, and take screenshots over SSH.

Works in 4 steps: Building and Deploying Chrome → Reading Logs on the Device → Taking Screenshots → …
Working with remote Chromebook testing hardware
SKILL.md covers 1. Building and Deploying Chrome, 2. Reading Logs on the Device, 3. Taking Screenshots and 4. Emulating Input & ChromeVox…
Calls ssh and scp

What it does

Physical Chromebook Debugging is an agent skill from nwjs/chromium.src. Build and deploy Chrome to a physical ChromeOS device, monitor logs, and take screenshots over SSH. Use when working with remote Chromebook testing hardware, deploying new builds of Chrome or ChromeOS, reading specific log files via SSH, or taking screenshots of a connected test endpoint.

Its SKILL.md is about 460 tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files (for example `EVAL.yaml` and `TEST.md`).

It sits in Development, covering Debugging. The repository describes itself as: Chromium codebase with NW.js modifications. Based on https://chromium.googlesource.com/chromium/src.git. The licence is BSD-3-Clause.

When your agent uses it

Working with remote Chromebook testing hardware
Deploying new builds of Chrome
Reading specific log files via SSH
Taking screenshots of a connected test endpoint

Example prompts

“/physical-chromebook-debugging”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

Building and Deploying Chrome
Reading Logs on the Device
Taking Screenshots
Emulating Input & ChromeVox Control

What it can do on your machine

Read from SKILL.md and the folder at commit a9e8946. 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:
- ssh
- scp
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use ssh and scp, 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

Physical Chromebook Debugging loads about 464 tokens when it runs. Until then it costs about 80 tokens; SKILL.md has 123 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~80
When it runs · the whole SKILL.md, loaded when a task matches: ~464

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.

SKILL.md

The full file from nwjs/chromium.src at commit a9e8946, republished under its BSD-3-Clause licence (© nwjs). 123 words, ~464 tokens.

Download SKILL.mdSave it as .claude/skills/physical-chromebook-debugging/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.

name: physical-chromebook-debugging
description: Build and deploy Chrome to a physical ChromeOS device, monitor logs, and take screenshots over SSH. Use when working with remote Chromebook testing hardware, deploying new builds of Chrome or ChromeOS, reading specific log files via SSH, or taking screenshots of a connected test endpoint.

Physical Chromebook Debugging Skills

This skill outlines how to perform standard tasks on a remote or local ChromeOS debugging device over SSH.

1. Building and Deploying Chrome

To build Chrome and deploy it to a remote ChromeOS device (or VM):

bash

autoninja -C out_strongbad/Release chrome
./third_party/chromite/bin/deploy_chrome --build-dir=out_strongbad/Release --device=localhost:2222 --board=strongbad

[!TIP] Replace out_strongbad/Release, localhost:2222, and strongbad with your actual configuration.

2. Reading Logs on the Device

Chrome logs are located in /var/log/chrome/chrome. View them via standard SSH filtering:

bash

ssh -p 2222 -i third_party/chromite/ssh_keys/testing_rsa root@localhost "grep -a 'SEARCH_TERM' /var/log/chrome/chrome"

3. Taking Screenshots

Capture a screenshot on the device and transfer it to your local machine with scp:

Take screenshot on the device:

bash

ssh -p 2222 -i third_party/chromite/ssh_keys/testing_rsa root@localhost "screenshot /tmp/screenshot.png"

Copy to your local machine:

bash

scp -P 2222 -i third_party/chromite/ssh_keys/testing_rsa root@localhost:/tmp/screenshot.png /path/to/local/dir/

4. Emulating Input & ChromeVox Control

For simulating key presses or toggling the ChromeVox screen reader on a physical Chromebook, please see the dedicated skill: chromevox-debugging-on-chromebook/SKILL.md

Files

SKILL.md and 3 other files in agents/skills/physical-chromebook-debugging of nwjs/chromium.src.

SKILL.md
EVAL.yaml
OWNERS
TEST.md

Open the folder on GitHubat commit a9e8946

Compare with similar skills

Physical Chromebook Debugging 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.

Physical Chromebook Debugging compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Physical Chromebook Debugging this skillnwjs/chromium.src	160	—	~464	Automated safety check: Pass	BSD-3-Clause	5 days ago
Trellis Session Insightmindfold-ai/Trellis	15k	4 repos	~1.7k	Automated safety check: Pass	AGPL-3.0	9 days ago
Native Data FetchingCherryHQ/cherry-studio-app	4k	6 repos	~2.9k	Automated safety check: Notes	MIT	today
Debugging Executionsn8n-io/n8n	207k	—	~2.6k	Automated safety check: Pass	Custom licence	today
Aoti Debugpytorch/pytorch	104k	1 repos	~1.7k	Automated safety check: Pass	Custom licence	today
Herdr Throwaway Reproductionherdrdev/herdr	43k	—	~2.4k	Automated safety check: Pass	Apache-2.0	yesterday

Similar skills

Trellis Session Insight
mindfold-ai/Trellis
Reach into past AI conversation history through the trellis mem CLI.
15k GitHub starsUsed in 4 repos~1.7k tokens
DevelopmentAuto-check passed
Native Data Fetching
CherryHQ/cherry-studio-app
A skill your agent uses when implementing or debugging ANY network request, API call, or data fetching.
4k GitHub starsUsed in 6 repos~2.9k tokens
DevelopmentAuto-check: notes
Debugging Executions
n8n-io/n8n
Official
Debug failed or wrong-output workflow executions using executions tools.
207k GitHub stars~2.6k tokensUpdated today
DevelopmentAuto-check passed
Aoti Debug
pytorch/pytorch
Debug AOTInductor (AOTI) errors and crashes. An agent skill from pytorch/pytorch.
104k GitHub starsUsed in 1 repo~1.7k tokens
DevelopmentAuto-check passed
Herdr Throwaway Reproduction
herdrdev/herdr
Runs a disposable, uniquely named Herdr session inside an existing one so runtime, pane, terminal or API bugs can be reproduced without touching the main session.
43k GitHub stars~2.4k tokensUpdated yesterday
DevelopmentAuto-check passed
Systematic Debugging
ultralisp/ultralisp
A skill your agent uses when encountering any bug, test failure, or unexpected behavior, before proposing fixes
258 GitHub starsUsed in 51 repos~2.4k tokens
DevelopmentAuto-check passed

More from nwjs/chromium.src

All 64 skills in this repo

Analyzing SQL Traces
nwjs/chromium.src
Extracts raw trace data from Perfetto traces, runs arbitrary SQL queries for custom follow-up analysis, and applies expert cognitive principles (Tiered Flow Analysis, Semantic Mismatch, Redundancy)…
160 GitHub stars~2.9k tokensUpdated 5 days ago
Auto-check passed
Chrome Performance Optimizer
nwjs/chromium.src
Autonomous multi-agent performance optimization loop for Chromium and V8.
160 GitHub stars~4.2k tokensUpdated 5 days ago
Auto-check passed
Automated Tracing
nwjs/chromium.src
Automated Tracing & Performance Telemetry in Chromium using Perfetto and Telemetry benchmarks.
160 GitHub stars~1.5k tokensUpdated 5 days ago
Auto-check passed
Chrome Releases
nwjs/chromium.src
Queries Chrome commit, version, release, and milestone metadata.
160 GitHub stars~1.3k tokensUpdated 5 days ago
Auto-check passed
Chromium Docs
nwjs/chromium.src
Search and reference Chromium documentation from the local docs index, including design docs, APIs, and development guides.
160 GitHub stars~1.2k tokensUpdated 5 days ago
Auto-check passed
Gn Deps Debugging
nwjs/chromium.src
Diagnose Chromium GN dependency and include-visibility failures, including BUILD.gn deps/publicdeps, DEPS include rules, private headers, and circular dependencies.
160 GitHub stars~1.5k tokensUpdated 5 days ago
Auto-check passed

Questions about Physical Chromebook Debugging

What does Physical Chromebook Debugging do?

Build and deploy Chrome to a physical ChromeOS device, monitor logs, and take screenshots over SSH. src. Build and deploy Chrome to a physical ChromeOS device, monitor logs, and take screenshots over SSH.

When should I use Physical Chromebook Debugging?

Physical Chromebook Debugging fits situations like: working with remote Chromebook testing hardware; deploying new builds of Chrome; reading specific log files via SSH; taking screenshots of a connected test endpoint.

How do I install Physical Chromebook Debugging in Claude Code?

Run `npx skills add nwjs/chromium.src --skill physical-chromebook-debugging -a claude-code`. Or copy the skill folder (agents/skills/physical-chromebook-debugging in nwjs/chromium.src) into .claude/skills/physical-chromebook-debugging in your project. Claude Code loads it when a task matches its description.

How do I install Physical Chromebook Debugging in Codex?

Run `npx skills add nwjs/chromium.src --skill physical-chromebook-debugging -a codex`. Or copy the skill folder (agents/skills/physical-chromebook-debugging in nwjs/chromium.src) into .agents/skills/physical-chromebook-debugging in your project. Codex loads it when a task matches its description.

Can I use Physical Chromebook Debugging 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 nwjs/chromium.src --skill physical-chromebook-debugging -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/physical-chromebook-debugging, .gemini/skills/physical-chromebook-debugging, .github/skills/physical-chromebook-debugging and .opencode/skills/physical-chromebook-debugging in your project.

What does Physical Chromebook Debugging need to run?

Going by SKILL.md and its folder, Physical Chromebook Debugging needs the command-line tools its instructions call (ssh and scp).

Does Physical Chromebook Debugging access the network?

SKILL.md contains no URLs. Its commands use ssh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Physical Chromebook Debugging 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 Physical Chromebook Debugging use?

Physical Chromebook Debugging 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 Physical Chromebook Debugging use?

About 464 tokens (SKILL.md is roughly 1.9k 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 Physical Chromebook Debugging?

Skills that share tags, products or a category with Physical Chromebook Debugging: Trellis Session Insight (mindfold-ai/Trellis, 15k stars), Native Data Fetching (CherryHQ/cherry-studio-app, 4k stars), Debugging Executions (n8n-io/n8n, 207k stars) and Aoti Debug (pytorch/pytorch, 104k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Physical Chromebook Debugging?

nwjs (a GitHub organization) maintains it in nwjs/chromium.src, which has 160 GitHub stars. The repository holds 64 skills in this directory. The repository was last updated on October 3, 2026.

Source: nwjs/chromium.src on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Physical Chromebook Debugging

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Physical Chromebook Debugging Skills

1. Building and Deploying Chrome

2. Reading Logs on the Device

3. Taking Screenshots

4. Emulating Input & ChromeVox Control

Files

Compare with similar skills

Similar skills

More from nwjs/chromium.src

Related

Questions about Physical Chromebook Debugging