New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Experimental Code Coverage Build Invoker

by nwjs in nwjs/chromium.src

Triggers LUCI try jobs to generate code coverage data. An agent skill from nwjs/chromium.src.

BSD-3-ClauseAuto-check passedTesting & QA

Install Experimental Code Coverage Build Invoker

skills CLI
$ npx skills add nwjs/chromium.src --skill experimental-code-coverage-build-invoker -a claude-code

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

GitHub CLI
$ gh skill install nwjs/chromium.src experimental-code-coverage-build-invoker --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-code-coverage-build-invoker .claude/skills/experimental-code-coverage-build-invoker && 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/

Facts

Skill name
experimental-code-coverage-build-invoker
GitHub stars
160
Token cost
~786 tokens
SKILL.md length
270 words
Files
1
Skills in repo
64
Repo updated
First seen
Licence
BSD-3-Clause

At a glance

Triggers LUCI try jobs to generate code coverage data. An agent skill from nwjs/chromium.src.

  • Works in 2 steps: Report the Buildbucket build links/URLs… → Write/update the build links in…
  • LUCI try jobs to generate code coverage data
  • SKILL.md covers When to Use This Skill, Inputs, Workflow Modes and Required Output & State Update, plus 2 more sections
  • Calls git and jq; reaches chromium-review.googlesource.com and ci.chromium.org

What it does

Experimental Code Coverage Build Invoker is an agent skill from nwjs/chromium.src. Triggers LUCI try jobs to generate code coverage data. Supports Mode 1 (standard git cl try for source CLs) and Mode 2 (led for custom builds).

Its SKILL.md is about 790 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 coverage. It works with Git. 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

  • LUCI try jobs to generate code coverage data
  • Tasks that involve Test coverage

Example prompts

  • “Use the experimental-code-coverage-build-invoker skill to trigger LUCI try jobs to generate code coverage data. An agent skill from nwjs/chromium.src”
  • “/experimental-code-coverage-build-invoker”

Workflow steps

2 steps, taken from the first numbered list in SKILL.md.

  1. Report the Buildbucket build links/URLs for the scheduled jobs mapped to builder name
  2. Write/update the build links in scratch/triage_state.json mapped to builder name under control_builds (if cl_url matches control_cl) or…

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:

    • git
    • jq

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • chromium-review.googlesource.com
    • ci.chromium.org

    Also links to:

    • g3doc.corp.google.com
    • chromium.googlesource.com

    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 Code Coverage Build Invoker loads about 786 tokens when it runs. Until then it costs about 46 tokens; SKILL.md has 270 words of instructions outside code blocks.

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

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). 270 words, ~786 tokens.

Download SKILL.mdSave it as .claude/skills/experimental-code-coverage-build-invoker/SKILL.md (or your agent's skills folder).
name
experimental-code-coverage-build-invoker
description
Triggers LUCI try jobs to generate code coverage data. Supports Mode 1 (standard git cl try for source CLs) and Mode 2 (led for custom builds).

Code Coverage Build Invoker

This skill schedules LUCI try jobs to generate code coverage data. It provides two distinct operational modes based on what is being tested.

When to Use This Skill

Activate this skill when:

  • Triggering verification try jobs on a pending Gerrit CL (git cl try).
  • Comparing baseline coverage against experimental patchsets.
  • Testing local uncommitted recipe modifications or custom build properties (led).

Inputs

  • cl_url: The full URL to the Gerrit CL (e.g., https://chromium-review.googlesource.com/c/chromium/src/+/7916168).
  • builders_of_concern: A list of builder names to trigger (e.g., ["android-x86-rel", "linux-rel"]).

Workflow Modes

Mode 1: Standard CL Verification (git cl try)

Use this mode for submitted or WIP Gerrit CLs modifying application source code (.cc, .java) or Starlark builder configurations (.star).

Execute the command from the repository root:

bash
git cl try -B luci.chromium.try -b builder1 -b builder2
Mode 2: Low-Level Build Dispatch (led)

Use this mode exclusively for debugging unlanded recipe changes, custom build properties, or reproducing historical Swarming runs.

For each target builder, fetch the builder definition, apply unmerged CL modifications (or local recipe bundle), explicitly set the Swarming priority to match standard CQ tryjob traffic (priority = 30), and dispatch:

bash
# Example for patching a CL and setting CQ priority via LED
led get-builder luci.chromium.try:android-x86-rel \
  | led edit-gerrit-cl <cl_url> \
  | jq '.buildbucket.bbagent_args.build.infra.backend.config.priority = 30' \
  | led launch
Example: Testing Local Recipe Modifications

To test unmerged local recipe edits at standard CQ tryjob priority:

bash
led get-builder luci.chromium.try:android-x86-rel \
  | led edit-recipe-bundle \
  | jq '.buildbucket.bbagent_args.build.infra.backend.config.priority = 30' \
  | led launch

Required Output & State Update

  1. Report the Buildbucket build links/URLs for the scheduled jobs mapped to builder name (e.g., {"linux-rel": "https://ci.chromium.org/b/8679163306673603153"}).
  2. Write/update the build links in scratch/triage_state.json mapped to builder name under control_builds (if cl_url matches control_cl) or fix_builds (if cl_url matches fix_cl).

Important Considerations

  • Authentication: Ensure gcert / luci-auth tokens are valid.
  • Syntactic Bucket: Note warnings suggesting chromium/try, but -B luci.chromium.try is syntactically required by git cl try.

References

© 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

Just SKILL.md in agents/skills/experimental-code-coverage-build-invoker of nwjs/chromium.src.

Open the folder on GitHubat commit a9e8946

Compare with similar skills

Experimental Code Coverage Build Invoker 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 Code Coverage Build Invoker compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Experimental Code Coverage Build Invoker this skillnwjs/chromium.src160—~786Automated safety check: PassBSD-3-Clause
Evaluate PR Testsdotnet/maui23k—~2.9kAutomated safety check: PassMIT
Test RoadmapOvid/paad131—~2.3kAutomated safety check: PassMIT
Test Writer for Changed Codeposhan0126/dotclaude871—~1.2kAutomated safety check: PassMIT
Wf Spec Review Implchangkun/wallfacer112—~1.1kAutomated safety check: PassMIT
Write TestsNeoLabHQ/context-engineering-kit1.7k—~2kAutomated safety check: PassGPL-3.0

Similar skills

  • Evaluate PR Tests

    dotnet/maui

    Official

    Reviews the tests added in a pull request for fix coverage, quality, edge cases and test type, and recommends lighter test types where they would do.

    23k GitHub stars~2.9k tokensUpdated today
    Testing & QAAuto-check passed

  • Test Roadmap

    Ovid/paad

    EXPERIMENTAL. An agent skill from Ovid/paad.

    131 GitHub stars~2.3k tokensUpdated yesterday
    Testing & QAAuto-check passed

  • Test Writer for Changed Code

    poshan0126/dotclaude

    Writes tests for newly added or changed code by reading the git diff, mapping every code path and writing one-assertion tests that match the project's conventions.

    871 GitHub stars~1.2k tokensUpdated 1 mo ago
    Testing & QAAuto-check passed

  • Wf Spec Review Impl

    changkun/wallfacer

    Read-only verdict on whether an implementation meets its spec: each acceptance criterion classified, unintended changes flagged, test coverage checked.

    112 GitHub stars~1.1k tokensUpdated 4 days ago
    Testing & QAAuto-check passed

  • Write Tests

    NeoLabHQ/context-engineering-kit

    Add missing test coverage for your local code changes by generating new test files (covers uncommitted and untracked changes, or the latest commit if everything is committed).

    1.7k GitHub stars~2k tokensUpdated 1 mo ago
    Testing & QAAuto-check passed

  • Review

    atelier-fashion/adlc-toolkit

    Multi-agent code review covering correctness, quality, architecture, test coverage, and security

    171 GitHub stars~1.9k tokensUpdated 9 days 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 4 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 4 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 4 days ago
    Auto-check passed

  • Chrome Releases

    nwjs/chromium.src

    Queries Chrome commit, version, release, and milestone metadata.

    160 GitHub stars~1.3k tokensUpdated 4 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 4 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 4 days ago
    Auto-check passed

Works with

Categories

Questions about Experimental Code Coverage Build Invoker

What does Experimental Code Coverage Build Invoker do?

Triggers LUCI try jobs to generate code coverage data. An agent skill from nwjs/chromium.src. src. Triggers LUCI try jobs to generate code coverage data.

When should I use Experimental Code Coverage Build Invoker?

Experimental Code Coverage Build Invoker fits situations like: LUCI try jobs to generate code coverage data; tasks that involve Test coverage.

How do I install Experimental Code Coverage Build Invoker in Claude Code?

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

How do I install Experimental Code Coverage Build Invoker in Codex?

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

Can I use Experimental Code Coverage Build Invoker 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-code-coverage-build-invoker -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-code-coverage-build-invoker, .gemini/skills/experimental-code-coverage-build-invoker, .github/skills/experimental-code-coverage-build-invoker and .opencode/skills/experimental-code-coverage-build-invoker in your project.

What does Experimental Code Coverage Build Invoker need to run?

Going by SKILL.md and its folder, Experimental Code Coverage Build Invoker needs the command-line tools its instructions call (git and jq).

Does Experimental Code Coverage Build Invoker access the network?

SKILL.md names 4 domains. In commands or code: chromium-review.googlesource.com and ci.chromium.org; the agent is likely to contact these when it follows the instructions. As links in the text: g3doc.corp.google.com and chromium.googlesource.com. This is read from the text; nothing was executed.

Is Experimental Code Coverage Build Invoker 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 Code Coverage Build Invoker use?

Experimental Code Coverage Build Invoker 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 Code Coverage Build Invoker use?

About 786 tokens (SKILL.md is roughly 3.1k 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 Code Coverage Build Invoker?

Skills that share tags, products or a category with Experimental Code Coverage Build Invoker: Evaluate PR Tests (dotnet/maui, 23k stars), Test Roadmap (Ovid/paad, 131 stars), Test Writer for Changed Code (poshan0126/dotclaude, 871 stars) and Wf Spec Review Impl (changkun/wallfacer, 112 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Experimental Code Coverage Build Invoker?

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.