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

Chrome Releases

by nwjs in nwjs/chromium.src

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

BSD-3-ClauseAuto-check passedProduct & Project Management

Install Chrome Releases

skills CLI
$ npx skills add nwjs/chromium.src --skill chrome-releases -a claude-code

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

GitHub CLI
$ gh skill install nwjs/chromium.src chrome-releases --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/chrome-releases .claude/skills/chrome-releases && 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
chrome-releases
GitHub stars
160
Token cost
~1.3k tokens
SKILL.md length
557 words
Files
4 (incl. scripts)
Skills in repo
64
Repo updated
First seen
Licence
BSD-3-Clause

At a glance

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

  • Works in 8 steps: Look Up a Commit (commit) → Look Up a Version (version) → Look Up a Milestone (milestone) → …
  • Finding the first landed Chrome version of a commit
  • SKILL.md covers Capabilities & Commands and Workflows
  • Runs Python scripts from its folder; calls python3

What it does

Chrome Releases is an agent skill from nwjs/chromium.src. Queries Chrome commit, version, release, and milestone metadata. Use when finding the first landed Chrome version of a commit, checking channel releases across platforms, inspecting milestone schedules and branch refs, or checking version containment.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including scripts (for example `scripts/chrome_releases.py` and `scripts/chrome_releases_test.py`).

It sits in Product & Project Management, covering Project management. 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

  • Finding the first landed Chrome version of a commit
  • Checking channel releases across platforms
  • Inspecting milestone schedules and branch refs
  • Checking version containment

Example prompts

  • “Use the chrome-releases skill to query Chrome commit, version, release, and milestone metadata”
  • “/chrome-releases”

Requirements

  • Python 3

Workflow steps

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

  1. Look Up a Commit (commit)
  2. Look Up a Version (version)
  3. Look Up a Milestone (milestone)
  4. Find Where a Commit Landed and Released
  5. Track a Subproject Commit (V8, Skia) into Chrome
  6. Determine if Commit Version A is in Release Version B
  7. Find the Release Branch and Latest Version for a Milestone
  8. Check Milestone Deadlines for a Pending Change

What it can do on your machine

Read from SKILL.md and the folder at commit 7b52561. 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:

    • 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

Chrome Releases loads about 1.3k tokens when it runs. Until then it costs about 67 tokens; SKILL.md has 557 words of instructions outside code blocks.

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

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 7b52561, republished under its BSD-3-Clause licence (© nwjs). 557 words, ~1,308 tokens.

Download SKILL.mdSave it as .claude/skills/chrome-releases/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
chrome-releases
description
Queries Chrome commit, version, release, and milestone metadata. Use when finding the first landed Chrome version of a commit, checking channel releases across platforms, inspecting milestone schedules and branch refs, or checking version containment.

Chrome Releases & Commit Tracker

Queries relationships between Chrome commits, versions, releases, and milestones using the Developer Graph API via chrome_releases.py.

Capabilities & Commands

1. Look Up a Commit (commit)

Returns Git metadata, associated Gerrit changes, derived commit relations (cherry picks, reverts, relands), and the earliest version tag ("first landed" version).

bash
python3 agents/skills/chrome-releases/scripts/chrome_releases.py commit <COMMIT_HASH>

Key Fields in Response:

  • chromeMetadata.commitPosition: The commit position number.
  • chromeMetadata.versions: Earliest version tags containing this commit.
    • For Chromium commits: Contains the Chrome version (e.g. 136.0.7051.0).
    • For sub-repo commits (e.g. V8): Contains the sub-repo version and the first Chromium version that rolled it in.
  • sourceCommits / derivedCommits: Related commits (CHERRY_PICK, REVERT, RELAND, DEPENDENCY_ADD, DEPENDENCY_REMOVE).
  • gerritChanges: Change number, Change-Id, host, project, and branch.
2. Look Up a Version (version)

Returns the Git commit hash, parent version, minibranch info, and first release on each platform and channel.

bash
python3 agents/skills/chrome-releases/scripts/chrome_releases.py version <VERSION_OR_ALIAS>

Aliases:

  • latest-main: Latest version on the main trunk.
  • latest-{branch}: Latest version on a release branch (e.g. latest-7103).
  • latest-{branch}_{minibranch}: Latest version on a minibranch (e.g. latest-7103_160).

Key Fields in Response:

  • chromeMetadata.parentVersion: Immediately preceding version in the version tree.
  • chromeMetadata.minibranch: Patch number on the parent branch if this version is on a minibranch.
  • chromeMetadata.firstReleases: First releases of this version by platform and channel (e.g. mac/stable, android/beta, win/canary), including release version and start timestamp.
3. Look Up a Milestone (milestone)

Returns the release branch and scheduled lifecycle event dates for a major Chrome milestone.

bash
python3 agents/skills/chrome-releases/scripts/chrome_releases.py milestone <MILESTONE>

Key Fields in Response:

  • branches: Branch refs (e.g. refs/branch-heads/6723) and the main-branch divergence commit hash.
  • events: Scheduled dates for milestone events:
    • branch_point: Branch creation date.
    • final_beta_cut / stable_cut: Code freeze/cut dates.
    • earliest_beta / final_beta: Beta rollout dates.
    • early_stable: Early stable rollout date (~0.5% users).
    • stable_date: Stable release date (100% rollout).
    • stable_refresh_first, stable_refresh_second, stable_refresh_third: Bi-weekly refresh dates.
    • feature_freeze, late_stable_date, chromeos_*: ChromeOS specific milestone events.

Workflows

1. Find Where a Commit Landed and Released
  1. Run commit with <commit_hash>.
  2. Read chromeMetadata.versions to find the Chrome "First Landed" version (e.g. 136.0.7051.0).
  3. Run version with <first_landed_version> to read firstReleases for target platforms/channels.
Show full SKILL.md (236 more words)Show less
2. Track a Subproject Commit (V8, Skia) into Chrome
  1. Run commit with <subproject_commit_hash>.
  2. Inspect chromeMetadata.versions. It lists:
    • The subproject version (e.g. V8 12.0.0.0).
    • The first Chrome version that included the dependency roll (e.g. Chrome 120.0.6099.0).
  3. Run version with the Chrome version to find the Chrome releases that include the roll.
3. Determine if Commit Version A is in Release Version B

Version numbers follow Major.Minor.Build.Patch (e.g. 136.0.7051.0).

Use this rule to determine if version A is an ancestor of version B:

  • Main branch (A.Patch == 0): A is in B if A.Build <= B.Build.
  • Release branch (A.Patch > 0, no minibranch): A is in B if A.Build == B.Build and A.Patch <= B.Patch.
  • Minibranch (A.Minibranch > 0): A is in B if B is on the same minibranch (A.Build == B.Build, A.Minibranch == B.Minibranch, and A.Patch <= B.Patch).
4. Find the Release Branch and Latest Version for a Milestone
  1. Run milestone with <milestone> to get the branch ref under branches (e.g. refs/branch-heads/7103 -> branch number 7103).
  2. Run version with latest-{branch_number} (e.g. latest-7103) to find the latest version on that release branch.
5. Check Milestone Deadlines for a Pending Change
  1. Call version with latest-main to see the current main trunk build number.
  2. Call milestone with the upcoming <milestone> to read events dates (branch_point, stable_cut, stable_date).
  3. If a change lands before the branch_point date, it lands in that milestone automatically. If it lands after, it requires a cherry-pick to refs/branch-heads/{branch_number}.

© 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 3 other files (scripts) in agents/skills/chrome-releases of nwjs/chromium.src.

  • SKILL.md
  • OWNERS
  • scripts/chrome_releases.py
  • scripts/chrome_releases_test.py

Open the folder on GitHubat commit 7b52561

Compare with similar skills

Chrome Releases 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.

Chrome Releases compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Chrome Releases this skillnwjs/chromium.src160—~1.3kAutomated safety check: PassBSD-3-Clause
CCPM Project Managementautomazeio/ccpm8.4k—~1.1kAutomated safety check: PassMIT
Uvastral-sh/claude-code-plugins3132 repos~980Automated safety check: PassApache-2.0
Project Managementkunchenguid/firstmate7.8k—~2.1kAutomated safety check: PassMIT
Hivemind Goalsactiveloopai/hivemind1.6k—~1.7kAutomated safety check: NotesApache-2.0
Ichartjswanghetommy/ichartjs352—~4.3kAutomated safety check: PassApache-2.0

Similar skills

  • CCPM Project Management

    automazeio/ccpm

    Runs a spec-driven workflow from PRD to epic to GitHub issues to parallel agents, with status, standup and blocked-work reports from bundled scripts.

    8.4k GitHub stars~1.1k tokensUpdated 6 mo ago
    Product & Project ManagementAuto-check passed

  • Uv

    astral-sh/claude-code-plugins

    Official

    Guide for using uv, the Python package and project manager. An agent skill from astral-sh/claude-code-plugins.

    313 GitHub starsUsed in 2 repos~980 tokens
    Product & Project ManagementAuto-check passed

  • Project Management

    kunchenguid/firstmate

    Agent-only procedure for Firstmate project management. An agent skill from kunchenguid/firstmate.

    7.8k GitHub stars~2.1k tokensUpdated today
    Product & Project ManagementAuto-check passed

  • Hivemind Goals

    activeloopai/hivemind

    Create, track and update team goals via the Deeplake virtual filesystem at memory/goal/.

    1.6k GitHub stars~1.7k tokensUpdated 12 days ago
    Product & Project ManagementAuto-check: notes

  • Ichartjs

    wanghetommy/ichartjs

    Plan, validate, render, explain, and safely edit iChart.js visualizations from tabular, project, or diagram data.

    352 GitHub stars~4.3k tokensUpdated yesterday
    Product & Project ManagementAuto-check passed

  • Hivemind Goals

    activeloopai/hivemind

    Create, track and update team goals in Hivemind via the hivemind CLI.

    1.6k GitHub stars~814 tokensUpdated 12 days ago
    Product & Project ManagementAuto-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 today
    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 today
    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 today
    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 today
    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 today
    Auto-check passed

  • Histogram Extension

    nwjs/chromium.src

    Extension pipeline to bump expiration dates of Chromium UMA histograms.

    160 GitHub stars~503 tokensUpdated today
    Auto-check passed

Categories

Questions about Chrome Releases

What does Chrome Releases do?

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

When should I use Chrome Releases?

Chrome Releases fits situations like: finding the first landed Chrome version of a commit; checking channel releases across platforms; inspecting milestone schedules and branch refs; checking version containment.

How do I install Chrome Releases in Claude Code?

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

How do I install Chrome Releases in Codex?

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

Can I use Chrome Releases 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 chrome-releases -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/chrome-releases, .gemini/skills/chrome-releases, .github/skills/chrome-releases and .opencode/skills/chrome-releases in your project.

What does Chrome Releases need to run?

Going by SKILL.md and its folder, Chrome Releases needs Python for the scripts in its folder and the command-line tools its instructions call (python3). Our summary lists: Python 3.

Does Chrome Releases 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 Chrome Releases 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 Chrome Releases use?

Chrome Releases 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 Chrome Releases use?

About 1.3k tokens (SKILL.md is roughly 5.2k 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 Chrome Releases?

Skills that share tags, products or a category with Chrome Releases: CCPM Project Management (automazeio/ccpm, 8.4k stars), Uv (astral-sh/claude-code-plugins, 313 stars), Project Management (kunchenguid/firstmate, 7.8k stars) and Hivemind Goals (activeloopai/hivemind, 1.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Chrome Releases?

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 10, 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.