PR Design Doc
OpenHands/OpenHands
For a non-trivial pull request, write a self-contained HTML design doc under the temporary .pr/ directory and link a visibility-appropriate preview in the PR description, so maintainers grasp the…
Search and reference Chromium documentation from the local docs index, including design docs, APIs, and development guides.
Install Chromium Docs
$ npx skills add nwjs/chromium.src --skill chromium-docs -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install nwjs/chromium.src chromium-docs --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/nwjs/chromium.src.git skills-src && mkdir -p .claude/skills && cp -r skills-src/agents/skills/chromium-docs .claude/skills/chromium-docs && rm -rf skills-srcUse ~/.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/
Install the "chromium-docs" agent skill from https://github.com/nwjs/chromium.src/tree/main/agents/skills/chromium-docs into .claude/skills/chromium-docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "chromium-docs", 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 install https://github.com/nwjs/chromium.src/tree/main/agents/skills/chromium-docsType 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.
$ npx skills add nwjs/chromium.src --skill chromium-docs -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install nwjs/chromium.src chromium-docs --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nwjs/chromium.src.git skills-src && mkdir -p .agents/skills && cp -r skills-src/agents/skills/chromium-docs .agents/skills/chromium-docs && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "chromium-docs" agent skill from https://github.com/nwjs/chromium.src/tree/main/agents/skills/chromium-docs into .agents/skills/chromium-docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "chromium-docs", 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.
$ npx skills add nwjs/chromium.src --skill chromium-docs -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install nwjs/chromium.src chromium-docs --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nwjs/chromium.src.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/agents/skills/chromium-docs .cursor/skills/chromium-docs && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "chromium-docs" agent skill from https://github.com/nwjs/chromium.src/tree/main/agents/skills/chromium-docs into .cursor/skills/chromium-docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "chromium-docs", 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 https://github.com/nwjs/chromium.src.git --path agents/skills/chromium-docs--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add nwjs/chromium.src --skill chromium-docs -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install nwjs/chromium.src chromium-docs --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nwjs/chromium.src.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/agents/skills/chromium-docs .gemini/skills/chromium-docs && rm -rf skills-srcUse ~/.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/
Install the "chromium-docs" agent skill from https://github.com/nwjs/chromium.src/tree/main/agents/skills/chromium-docs into .gemini/skills/chromium-docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "chromium-docs", 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.
$ gh skill install nwjs/chromium.src chromium-docsInstalls 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).
$ npx skills add nwjs/chromium.src --skill chromium-docs -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/nwjs/chromium.src.git skills-src && mkdir -p .github/skills && cp -r skills-src/agents/skills/chromium-docs .github/skills/chromium-docs && rm -rf skills-srcUse ~/.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/
Install the "chromium-docs" agent skill from https://github.com/nwjs/chromium.src/tree/main/agents/skills/chromium-docs into .github/skills/chromium-docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "chromium-docs", 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.
$ npx skills add nwjs/chromium.src --skill chromium-docs -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install nwjs/chromium.src chromium-docs --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nwjs/chromium.src.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/agents/skills/chromium-docs .opencode/skills/chromium-docs && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "chromium-docs" agent skill from https://github.com/nwjs/chromium.src/tree/main/agents/skills/chromium-docs into .opencode/skills/chromium-docs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "chromium-docs", 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
chromium-docs- GitHub stars
- 160
- Token cost
- ~1.2k tokens
- SKILL.md length
- 493 words
- Files
- 7 (incl. scripts)
- Skills in repo
- 64
- Repo updated
- First seen
- Licence
- BSD-3-Clause
At a glance
Search and reference Chromium documentation from the local docs index, including design docs, APIs, and development guides.
- Works in 2 steps: Run the --build-index command shown above → Retry the original search
- The user asks to find
- SKILL.md covers When to activate, Usage, Index maintenance and Error handling, plus 4 more sections
- Runs Python scripts from its folder; calls python3 and git
What it does
Chromium Docs is an agent skill from nwjs/chromium.src. Search and reference Chromium documentation from the local docs index, including design docs, APIs, and development guides. Use when the user asks to find, locate, browse, or learn from Chromium docs about architecture, APIs, testing, GPU, networking, or other Chromium topics.
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 9 other files, including scripts (for example `README.md`, `data/configs/search_config.json` and `scripts/chromium_docs.py`).
It sits in Development, covering Architecture decision records. 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
- The user asks to find
- Learn from Chromium docs about architecture
- Other Chromium topics
Example prompts
- “/chromium-docs”
Requirements
- Python 3
Workflow steps
2 steps, taken from the first numbered list in SKILL.md.
- Run the --build-index command shown above
- Retry the original search
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
Ships 2 files in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
python3git
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
Chromium Docs loads about 1.2k tokens when it runs. Until then it costs about 73 tokens; SKILL.md has 493 words of instructions outside code blocks.
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); the scripts in this folder are not scanned.
SKILL.md
The full file from nwjs/chromium.src at commit a9e8946, republished under its BSD-3-Clause licence (© nwjs). 493 words, ~1,189 tokens.
Download SKILL.mdSave it as
.claude/skills/chromium-docs/SKILL.md (or your agent's skills folder). This skill also uses 6 other files; get the full folder from GitHub.- name
- chromium-docs
- description
- Search and reference Chromium documentation from the local docs index, including design docs, APIs, and development guides. Use when the user asks to find, locate, browse, or learn from Chromium docs about architecture, APIs, testing, GPU, networking, or other Chromium topics.
Chromium Documentation Search
When to activate
Activate this skill when the user:
- Asks to find or locate Chromium documentation (e.g. "where are the Mojo docs?", "find the site-isolation design doc")
- Asks how to learn/use/understand a Chromium subsystem or concept and expects documentation references (e.g. "how to learn mojom", "how to understand site isolation docs")
- Needs documentation links for a component or subsystem (e.g. "GPU docs", "network stack references")
- Wants to browse what documentation exists for a topic or category
Do NOT activate when:
- The user asks to implement, modify, or debug code without requesting documentation references.
- The user already provided an exact file path and only wants the file content explained.
- The request is unrelated to Chromium documentation lookup (for example, general programming Q&A).
- The user asks for build/test execution only and does not need supporting docs.
Usage
Build the index (required before first search; rebuild after major syncs):
python3 agents/skills/chromium-docs/scripts/chromium_docs.py \
--build-indexSearch documentation:
python3 agents/skills/chromium-docs/scripts/chromium_docs.py \
"your query"Index maintenance
The index should be rebuilt when:
- First use — no index exists yet
- After a major
git pullor rebase — new docs may have been added - Search results seem stale or incomplete
The index covers ~2000+ markdown files and builds in about 30 seconds.
Error handling
If the search returns "index needs to be built first":
- Run the
--build-indexcommand shown above - Retry the original search
Available categories
Documents are classified into the following categories. Use these names to understand result groupings:
| Category | Covers |
|---|---|
| android | Android-specific code and build docs |
| ios | iOS-specific docs |
| chromeos | ChromeOS / Ash docs |
| gpu | Graphics, WebGL, Vulkan, OpenGL |
| media | Audio, video, codecs |
| security | Sandbox, site-isolation, crypto, CORS |
| network | Net stack, QUIC, TCP, DNS, SSL/TLS |
| testing | Unit tests, browser tests, test frameworks |
| ui | Views, Aura, UI toolkit |
| accessibility | a11y, screen readers |
| build | GN, Ninja, compilation |
| performance | Benchmarks, memory, speed |
| api | Mojo/mojom interfaces |
| architecture | Design documents, multi-process model |
| development | DevTools, debugging, tools |
| general | Everything else |
Show full SKILL.md (182 more words)Show less
Interpreting results
Search results are returned as markdown with:
- Numbered entries with linked file paths:
[Title](path/to/doc.md) - A category label (e.g. Architecture, Testing, Network)
- A brief excerpt or summary showing matching context
When presenting results to the user:
- Show the top 3-5 most relevant results
- Include the file path so the user can open or read the document directly
- Briefly note what each document covers, based on the excerpt
- If no results are found, suggest alternative search terms or a different category
Examples
User asks: "How does Chromium's multi-process architecture work?"
Search
"multi-process architecture"and return the top design docs with file paths and summaries.
User asks: "Find all testing-related docs"
Search
"testing guide"to surface testing guides and frameworks.
User asks: "Where are the Mojo IPC docs?"
Search
"mojo ipc"and return linked paths to the Mojo binding and interface documentation.
User asks: "GPU rendering best practices"
Search
"gpu rendering"and present GPU-category results with excerpts.
Resources
- Search config:
agents/skills/chromium-docs/data/configs/search_config.json - README:
agents/skills/chromium-docs/README.md - Index scope: All
.mdfiles matchingdocs/**/*.md,*/README.md, and*/docs/*.mdacross the entire Chromium source tree
© nwjs, BSD-3-Clause. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 6 other files (scripts) in agents/skills/chromium-docs of nwjs/chromium.src.
- SKILL.md
- .gitignore
- OWNERS
- README.md
- data/configs/search_config.json
- scripts/chromium_docs.py
- scripts/chromium_docs_test.py
Open the folder on GitHubat commit a9e8946
Compare with similar skills
Chromium Docs 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Chromium Docs this skillnwjs/chromium.src | 160 | — | ~1.2k | Automated safety check: Pass | BSD-3-Clause | |
| PR Design DocOpenHands/OpenHands | 90k | — | ~2.4k | Automated safety check: Pass | MIT | |
| Cto AdvisorIbrahim-3d/orchestrator-supaconductor | 380 | 4 repos | ~2.4k | Automated safety check: Pass | MIT | |
| Improve Codebase Architectureywwynm/EverythingDone | 144 | 15 repos | ~1.3k | Automated safety check: Pass | GPL-3.0 | |
| Domain Modelingbrim-borium/spotify_sdk | 166 | 5 repos | ~806 | Automated safety check: Pass | Apache-2.0 | |
| Design Doc MermaidSpillwaveSolutions/design-doc-mermaid | 175 | 1 repos | ~5.6k | Automated safety check: Pass | None |
Similar skills
Cto Advisor
Ibrahim-3d/orchestrator-supaconductor
Technical leadership guidance for engineering teams, architecture decisions, and technology strategy.
Improve Codebase Architecture
ywwynm/EverythingDone
Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/.
Domain Modeling
brim-borium/spotify_sdk
Build and sharpen a project's domain model. An agent skill from brim-borium/spotify_sdk.
Design Doc Mermaid
SpillwaveSolutions/design-doc-mermaid
Create Mermaid diagrams (flowchart, sequence, class, ER, state, C4, architecture) from text or source code.
Learning Opportunities
DrCatHicks/learning-opportunities
Facilitates deliberate skill development during AI-assisted coding.
More from nwjs/chromium.src
All 64 skills in this repoAnalyzing 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)…
Chrome Performance Optimizer
nwjs/chromium.src
Autonomous multi-agent performance optimization loop for Chromium and V8.
Automated Tracing
nwjs/chromium.src
Automated Tracing & Performance Telemetry in Chromium using Perfetto and Telemetry benchmarks.
Chrome Releases
nwjs/chromium.src
Queries Chrome commit, version, release, and milestone metadata.
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.
Histogram Extension
nwjs/chromium.src
Extension pipeline to bump expiration dates of Chromium UMA histograms.
Related
Categories
Questions about Chromium Docs
What does Chromium Docs do?
Search and reference Chromium documentation from the local docs index, including design docs, APIs, and development guides. src. Search and reference Chromium documentation from the local docs index, including design docs, APIs, and development guides.
When should I use Chromium Docs?
Chromium Docs fits situations like: the user asks to find; learn from Chromium docs about architecture; other Chromium topics.
How do I install Chromium Docs in Claude Code?
Run `npx skills add nwjs/chromium.src --skill chromium-docs -a claude-code`. Or copy the skill folder (agents/skills/chromium-docs in nwjs/chromium.src) into .claude/skills/chromium-docs in your project. Claude Code loads it when a task matches its description.
How do I install Chromium Docs in Codex?
Run `npx skills add nwjs/chromium.src --skill chromium-docs -a codex`. Or copy the skill folder (agents/skills/chromium-docs in nwjs/chromium.src) into .agents/skills/chromium-docs in your project. Codex loads it when a task matches its description.
Can I use Chromium Docs 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 chromium-docs -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/chromium-docs, .gemini/skills/chromium-docs, .github/skills/chromium-docs and .opencode/skills/chromium-docs in your project.
What does Chromium Docs need to run?
Going by SKILL.md and its folder, Chromium Docs needs Python for the scripts in its folder and the command-line tools its instructions call (python3 and git). Our summary lists: Python 3.
Does Chromium Docs 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 Chromium Docs 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Chromium Docs use?
Chromium Docs 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 Chromium Docs use?
About 1.2k tokens (SKILL.md is roughly 4.8k 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 Chromium Docs?
Skills that share tags, products or a category with Chromium Docs: PR Design Doc (OpenHands/OpenHands, 90k stars), Cto Advisor (Ibrahim-3d/orchestrator-supaconductor, 380 stars), Improve Codebase Architecture (ywwynm/EverythingDone, 144 stars) and Domain Modeling (brim-borium/spotify_sdk, 166 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Chromium Docs?
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.