Agent skill

Experimental CI Only Validator

Checks if a Chromium test suite is barred by cionly = True configuration on coverage trybots, which prevents the test suite from running automatically on Gerrit CQ runs and can cause underreported…

BSD-3-ClauseAuto-check passedTesting & QA

Install Experimental CI Only Validator

skills CLI

$ npx skills add nwjs/chromium.src --skill experimental-ci-only-validator -a claude-code

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

GitHub CLI

$ gh skill install nwjs/chromium.src experimental-ci-only-validator --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/experimental-ci-only-validator .claude/skills/experimental-ci-only-validator && 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 "experimental-ci-only-validator" agent skill from https://github.com/nwjs/chromium.src/tree/main/agents/skills/experimental-ci-only-validator into .claude/skills/experimental-ci-only-validator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "experimental-ci-only-validator", 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/experimental-ci-only-validator

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 experimental-ci-only-validator -a codex

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

GitHub CLI

$ gh skill install nwjs/chromium.src experimental-ci-only-validator --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/experimental-ci-only-validator .agents/skills/experimental-ci-only-validator && 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 "experimental-ci-only-validator" agent skill from https://github.com/nwjs/chromium.src/tree/main/agents/skills/experimental-ci-only-validator into .agents/skills/experimental-ci-only-validator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "experimental-ci-only-validator", 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 experimental-ci-only-validator -a cursor

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

GitHub CLI

$ gh skill install nwjs/chromium.src experimental-ci-only-validator --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/experimental-ci-only-validator .cursor/skills/experimental-ci-only-validator && 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 "experimental-ci-only-validator" agent skill from https://github.com/nwjs/chromium.src/tree/main/agents/skills/experimental-ci-only-validator into .cursor/skills/experimental-ci-only-validator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "experimental-ci-only-validator", 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/experimental-ci-only-validator

--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 experimental-ci-only-validator -a gemini-cli

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

GitHub CLI

$ gh skill install nwjs/chromium.src experimental-ci-only-validator --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/experimental-ci-only-validator .gemini/skills/experimental-ci-only-validator && 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 "experimental-ci-only-validator" agent skill from https://github.com/nwjs/chromium.src/tree/main/agents/skills/experimental-ci-only-validator into .gemini/skills/experimental-ci-only-validator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "experimental-ci-only-validator", 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 experimental-ci-only-validator

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

At a glance

Checks if a Chromium test suite is barred by cionly = True configuration on coverage trybots, which prevents the test suite from running automatically on Gerrit CQ runs and can cause underreported…

Works in 2 steps: Checking Current Configuration (HEAD) → Checking Historical Configuration (at a…
Tasks that involve Test generation
SKILL.md covers When to Use This Skill and How to Use This Skill
Calls python3

What it does

Experimental CI Only Validator is an agent skill from nwjs/chromium.src. Checks if a Chromium test suite is barred by cionly = True configuration on coverage trybots, which prevents the test suite from running automatically on Gerrit CQ runs and can cause underreported code coverage.

Its SKILL.md is about 1k 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 Test generation and Test coverage. It works with JUnit. 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

Tasks that involve Test generation
Tasks that involve Test coverage

Example prompts

“Use the experimental-ci-only-validator skill to check if a Chromium test suite is barred by cionly = True configuration on coverage trybots, which…”
“/experimental-ci-only-validator”

Requirements

Python 3

Workflow steps

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

Checking Current Configuration (HEAD)
Checking Historical Configuration (at a revision)

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:
- python3
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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

Experimental CI Only Validator loads about 1k tokens when it runs. Until then it costs about 61 tokens; SKILL.md has 306 words of instructions outside code blocks.

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

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). 306 words, ~1,010 tokens.

Download SKILL.mdSave it as .claude/skills/experimental-ci-only-validator/SKILL.md (or your agent's skills folder).

name: experimental-ci-only-validator
description: Checks if a Chromium test suite is barred by `ci_only = True` configuration on coverage trybots, which prevents the test suite from running automatically on Gerrit CQ runs and can cause underreported code coverage.

CI-Only Validator Skill

This skill provides a quick way to check if a test suite has been configured as ci_only = True on the code coverage trybots.

When to Use This Skill

Use this skill when:

You are triaging an underreported code coverage bug on Gerrit.
You have already mapped the target source or test file to its parent executable test suite (e.g., using TestSuiteMapper).
You suspect that the test suite is configured on the coverage builders but is not executing in tryjobs.

How to Use This Skill

If you have identified the test suite name (e.g., chrome_junit_tests), run the quick check tool:

bash

python3 tools/code_coverage/ci_only_validator.py <test_suite_name>

Checking at a Past Revision (Historical Triage)

To verify the ci_only status of a test suite at a specific historical point (e.g., the revision of a Gerrit CL), pass the --revision (or -r) flag:

bash

python3 tools/code_coverage/ci_only_validator.py <test_suite_name> --revision <commit_hash_or_branch>

This is highly recommended for historical triaging because configurations on main might have changed since the CL was reviewed.

Interpreting the Results

The tool will scan CQ coverage trybots and coverage-specific trybots generated under infra/config/generated/builders/try/ and report their configuration for the target test suite:

ci_only = True: The test suite is barred from executing on this trybot by default during CQ runs. Gerrit coverage details for tests in this suite will not be generated automatically unless the developer explicitly requests them via a Gerrit footer.
ci_only = False: The test suite is allowed to run on the trybot in CQ.
Warning: Test suite ... was not found...: The test suite is not configured to run on any coverage trybots, meaning no coverage details are collected on CQ at all.

Example Runs

1. Checking Current Configuration (HEAD)

bash

python3 tools/code_coverage/ci_only_validator.py chrome_junit_tests

Output:

text

Checking test suite 'chrome_junit_tests' across 30 coverage trybots...
  Trybot: android-code-coverage          | Builder: chromium.coverage:android-code-coverage          | ci_only = True
  Trybot: android-desktop-x64-rel        | Builder: chromium.android.desktop:android-desktop-x64-rel-15-tests | ci_only = False
  Trybot: android-x86-code-coverage      | Builder: chromium.coverage:android-x86-code-coverage      | ci_only = True
  Trybot: android-x86-rel                | Builder: chromium.android:android-10-x86-nofieldtrial-rel | ci_only = True

This indicates that chrome_junit_tests is barred by ci_only = True in standard CQ at HEAD.

2. Checking Historical Configuration (at a revision)

bash

python3 tools/code_coverage/ci_only_validator.py chrome_junit_tests --revision verify-junit-coverage

Output:

text

Checking test suite 'chrome_junit_tests' across 30 coverage trybots at revision verify-junit-coverage...
  Trybot: android-code-coverage          | Builder: chromium.coverage:android-code-coverage          | ci_only = False
  Trybot: android-desktop-x64-rel        | Builder: chromium.android.desktop:android-desktop-x64-rel-15-tests | ci_only = False
  Trybot: android-x86-code-coverage      | Builder: chromium.coverage:android-x86-code-coverage      | ci_only = False
  Trybot: android-x86-rel                | Builder: chromium.android:android-10-x86-nofieldtrial-rel | ci_only = False

This indicates that on the verify-junit-coverage branch, the ci_only restriction has been successfully disabled.

Files

Just SKILL.md in agents/skills/experimental-ci-only-validator of nwjs/chromium.src.

Open the folder on GitHubat commit a9e8946

Compare with similar skills

Experimental CI Only Validator 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.

Experimental CI Only Validator compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Experimental CI Only Validator this skillnwjs/chromium.src	160	—	~1k	Automated safety check: Pass	BSD-3-Clause	5 days ago
TDD Guidealirezarezvani/claude-skills	28k	—	~3.4k	Automated safety check: Pass	MIT	1 mo ago
Test Qualitydecebals/claude-code-java	751	—	~3.8k	Automated safety check: Pass	MIT	1 mo ago
TDD GuideLeoYeAI/openclaw-master-skills	2.2k	—	~1.4k	Automated safety check: Pass	MIT	2 mo ago
Java Regression Test GeneratorArabelaTso/Skills-4-SE	253	—	~4k	Automated safety check: Pass	Apache-2.0	1 mo ago
Test Oracle GeneratorArabelaTso/Skills-4-SE	253	—	~3.5k	Automated safety check: Pass	Apache-2.0	1 mo ago

Similar skills

TDD Guide
alirezarezvani/claude-skills
Test-driven development skill for writing unit tests, generating test fixtures and mocks, analyzing coverage gaps, and guiding red-green-refactor workflows across Jest, Pytest, JUnit, Vitest, and…
28k GitHub stars~3.4k tokensUpdated 1 mo ago
Testing & QAAuto-check passed
Test Quality
decebals/claude-code-java
Write high-quality JUnit 5 tests with AssertJ assertions. An agent skill from decebals/claude-code-java.
751 GitHub stars~3.8k tokensUpdated 1 mo ago
Testing & QAAuto-check passed
TDD Guide
LeoYeAI/openclaw-master-skills
Test-driven development skill for writing unit tests, generating test fixtures and mocks, analyzing coverage gaps, and guiding red-green-refactor workflows across Jest, Pytest, JUnit, Vitest, and…
2.2k GitHub stars~1.4k tokensUpdated 2 mo ago
Testing & QAAuto-check passed
Java Regression Test Generator
ArabelaTso/Skills-4-SE
Automatically generate regression tests for Java codebases by analyzing changes between old and new code versions.
253 GitHub stars~4k tokensUpdated 1 mo ago
Testing & QAAuto-check passed
Test Oracle Generator
ArabelaTso/Skills-4-SE
Generates automated test oracles to verify correct software behavior.
253 GitHub stars~3.5k tokensUpdated 1 mo ago
Testing & QAAuto-check passed
Coverage Enhancer
ArabelaTso/Skills-4-SE
Analyze existing test suites and source code to suggest additional unit tests that improve test coverage.
253 GitHub stars~4.4k tokensUpdated 1 mo ago
Testing & QAAuto-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

Works with

JUnit

Questions about Experimental CI Only Validator

What does Experimental CI Only Validator do?

Checks if a Chromium test suite is barred by cionly = True configuration on coverage trybots, which prevents the test suite from running automatically on Gerrit CQ runs and can cause underreported…. src. Checks if a Chromium test suite is barred by cionly = True configuration on coverage trybots, which prevents the test suite from running automatically on Gerrit CQ runs and can cause underreported code coverage.

When should I use Experimental CI Only Validator?

Experimental CI Only Validator fits situations like: tasks that involve Test generation; tasks that involve Test coverage.

How do I install Experimental CI Only Validator in Claude Code?

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

How do I install Experimental CI Only Validator in Codex?

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

Can I use Experimental CI Only Validator 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 experimental-ci-only-validator -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/experimental-ci-only-validator, .gemini/skills/experimental-ci-only-validator, .github/skills/experimental-ci-only-validator and .opencode/skills/experimental-ci-only-validator in your project.

What does Experimental CI Only Validator need to run?

Going by SKILL.md and its folder, Experimental CI Only Validator needs the command-line tools its instructions call (python3). Our summary lists: Python 3.

Does Experimental CI Only Validator access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Experimental CI Only Validator 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 Experimental CI Only Validator use?

Experimental CI Only Validator 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 Experimental CI Only Validator use?

About 1k tokens (SKILL.md is roughly 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 Experimental CI Only Validator?

Skills that share tags, products or a category with Experimental CI Only Validator: TDD Guide (alirezarezvani/claude-skills, 28k stars), Test Quality (decebals/claude-code-java, 751 stars), TDD Guide (LeoYeAI/openclaw-master-skills, 2.2k stars) and Java Regression Test Generator (ArabelaTso/Skills-4-SE, 253 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Experimental CI Only Validator?

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 Experimental CI Only Validator

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

CI-Only Validator Skill

When to Use This Skill

How to Use This Skill

Checking at a Past Revision (Historical Triage)

Interpreting the Results

Example Runs

1. Checking Current Configuration (HEAD)

2. Checking Historical Configuration (at a revision)

Files

Compare with similar skills

Similar skills

More from nwjs/chromium.src

Related

Questions about Experimental CI Only Validator