Skip to content
TrustedSkillsbeta
Back to all skills

Electron Chromium Upgrade

Checked
electron·vlatest·frontend·MIT

Optimizes Chromium browser performance via dynamic resource allocation and advanced caching strategies.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add electron/electron --skill electron-chromium-upgrade -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

electron

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned electron/electron at 690ccdd890.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
690ccdd890
Manifest
.claude/skills/electron-chromium-upgrade/SKILL.md
Scanned
4 files, 590 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

The electron-chromium-upgrade skill allows AI agents to programmatically upgrade the Chromium runtime within Electron applications. It automates the process of fetching and installing newer versions of the Chromium engine to ensure apps remain compatible with modern web standards.

When to use it

  • Updating an existing Electron app to fix security vulnerabilities in the bundled Chromium version.
  • Ensuring compatibility with new web APIs that require a specific minimum Chromium version.
  • Automating maintenance pipelines for Electron-based desktop applications.
  • Resolving rendering issues caused by outdated browser engine features.

Key capabilities

  • Identifies current Chromium versions installed in Electron projects.
  • Fetches the latest stable or beta Chromium releases.
  • Executes automated upgrade scripts to replace bundled binaries.
  • Validates successful installation post-upgrade.

Example prompts

  • "Upgrade the Chromium version in my Electron project to the latest stable release."
  • "Check if my app is using an outdated Chromium engine and update it automatically."
  • "Run the electron-chromium-upgrade skill to patch security flaws in my desktop app."

Tips & gotchas

Ensure your build environment has write permissions for the node_modules directory before running upgrades. Always test application functionality after upgrading, as newer Chromium versions may introduce breaking changes for custom web content or plugins.