Uv Workflow
Aedelon/claude-code-blueprint
Master uv package manager for Python: project setup, dependency management, virtual environments, lockfiles, CI/CD integration, Docker builds, and migration from pip/poetry.
Bumps the pinned v8 and rusty_v8 versions in Codex, validates the release-candidate path with the v8-canary check, and traces failures to upstream build changes.
Install Update V8 Version
$ npx skills add openinterpreter/openinterpreter --skill update-v8-version -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install openinterpreter/openinterpreter update-v8-version --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/openinterpreter/openinterpreter.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/update-v8-version .claude/skills/update-v8-version && 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 "update-v8-version" agent skill from https://github.com/openinterpreter/openinterpreter/tree/main/.codex/skills/update-v8-version into .claude/skills/update-v8-version/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "update-v8-version", 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/openinterpreter/openinterpreter/tree/main/.codex/skills/update-v8-versionType 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 openinterpreter/openinterpreter --skill update-v8-version -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install openinterpreter/openinterpreter update-v8-version --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openinterpreter/openinterpreter.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.codex/skills/update-v8-version .agents/skills/update-v8-version && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "update-v8-version" agent skill from https://github.com/openinterpreter/openinterpreter/tree/main/.codex/skills/update-v8-version into .agents/skills/update-v8-version/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "update-v8-version", 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 openinterpreter/openinterpreter --skill update-v8-version -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install openinterpreter/openinterpreter update-v8-version --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openinterpreter/openinterpreter.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.codex/skills/update-v8-version .cursor/skills/update-v8-version && 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 "update-v8-version" agent skill from https://github.com/openinterpreter/openinterpreter/tree/main/.codex/skills/update-v8-version into .cursor/skills/update-v8-version/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "update-v8-version", 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/openinterpreter/openinterpreter.git --path .codex/skills/update-v8-version--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 openinterpreter/openinterpreter --skill update-v8-version -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install openinterpreter/openinterpreter update-v8-version --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openinterpreter/openinterpreter.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.codex/skills/update-v8-version .gemini/skills/update-v8-version && 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 "update-v8-version" agent skill from https://github.com/openinterpreter/openinterpreter/tree/main/.codex/skills/update-v8-version into .gemini/skills/update-v8-version/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "update-v8-version", 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 openinterpreter/openinterpreter update-v8-versionInstalls 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 openinterpreter/openinterpreter --skill update-v8-version -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/openinterpreter/openinterpreter.git skills-src && mkdir -p .github/skills && cp -r skills-src/.codex/skills/update-v8-version .github/skills/update-v8-version && 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 "update-v8-version" agent skill from https://github.com/openinterpreter/openinterpreter/tree/main/.codex/skills/update-v8-version into .github/skills/update-v8-version/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "update-v8-version", 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 openinterpreter/openinterpreter --skill update-v8-version -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install openinterpreter/openinterpreter update-v8-version --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openinterpreter/openinterpreter.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.codex/skills/update-v8-version .opencode/skills/update-v8-version && 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 "update-v8-version" agent skill from https://github.com/openinterpreter/openinterpreter/tree/main/.codex/skills/update-v8-version into .opencode/skills/update-v8-version/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "update-v8-version", 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
update-v8-version- GitHub stars
- 69k
- Used in
- 2 other repos
- Token cost
- ~845 tokens
- SKILL.md length
- 370 words
- Files
- 2
- Skills in repo
- 10
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Bumps the pinned v8 and rusty_v8 versions in Codex, validates the release-candidate path with the v8-canary check, and traces failures to upstream build changes.
- Works in 5 steps: Read third_party/v8/README.md and follow… → Inspect and update the concrete repo… → Keep the existing checksum helpers in… → …
- Bumping the pinned V8 or rusty_v8 version in Codex
- SKILL.md covers Core Workflow, Failure Path and Reporting
- Calls python3
What it does
The bump starts from third_party/v8/README.md, treated as the source of truth for the release sequence, then updates every place that carries the pin: the Cargo manifest and lockfile under codex-rs, MODULE.bazel, third_party/v8/BUILD.bazel, the README and, when prebuilt inputs change, the matching rusty_v8 sha256 manifest. Checksum helper commands in .github/scripts/rusty_v8_bazel.py update and check the module file, and a unit test file covers them.
Validation prefers the v8-canary CI result for the candidate branch or PR, read through GitHub check tooling or gh, and falls back to the closest practical local check while saying plainly that it is a substitute. If the canary passes the agent stops, summarizes and leaves tags, releases and pushes alone unless asked.
A failure path applies only when the canary or local build breaks. The agent captures the failing target, job and first useful error, compares the pinned and target versions in denoland/rusty_v8 and upstream V8, and tracks build-relevant differences such as binding layout, asset names, GN or Bazel targets, custom libc++ inputs, sandbox and pointer-compression relations, and patches that no longer apply. It then traces each one to Codex's build graph and changes only what is needed.
When your agent uses it
- Bumping the pinned V8 or rusty_v8 version in Codex
- Checking the v8-canary result for a release candidate
- Diagnosing why a V8 version update no longer builds
Example prompts
- “Update rusty_v8 to the next release and check the v8-canary result.”
- “The v8-canary job failed on the new version, so find the first real error.”
- “Compare the pinned V8 with the target tag and list the build-relevant changes.”
Requirements
- A checkout of the Codex repository
- Python 3 for the checksum helper scripts
- GitHub CLI (`gh`) or other GitHub check tooling
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Read third_party/v8/README.md and follow its version-bump sequence. Treat
- Inspect and update the concrete repo surfaces that carry the pin
- Keep the existing checksum helpers in the loop
- Validate the release-candidate path before broadening the work
- If the canary path passes, stop there. Summarize the result and encourage the
What it can do on your machine
Read from SKILL.md and the folder at commit cc054cf. 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
Update V8 Version loads about 845 tokens when it runs. Until then it costs about 83 tokens; SKILL.md has 370 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); files beside SKILL.md are not scanned.
SKILL.md
The full file from openinterpreter/openinterpreter at commit cc054cf, republished under its Apache-2.0 licence (© openinterpreter). 370 words, ~845 tokens.
Download SKILL.mdSave it as
.claude/skills/update-v8-version/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- update-v8-version
- description
- Update Codex's pinned `v8` / `rusty_v8` versions, validate the release-candidate path, and investigate failed V8 canary or artifact builds. Use when asked to bump V8, update `rusty_v8` artifacts, prepare or validate a V8 release candidate, check `v8-canary`, or diagnose why a V8 version update no longer builds.
Update V8 Version
Core Workflow
Read
third_party/v8/README.mdand follow its version-bump sequence. Treat that document as the release-process source of truth.Inspect and update the concrete repo surfaces that carry the pin:
codex-rs/Cargo.tomlcodex-rs/Cargo.lockMODULE.bazelthird_party/v8/BUILD.bazelthird_party/v8/README.md- the matching
third_party/v8/rusty_v8_<version>.sha256manifest when the remaining prebuilt inputs change
Keep the existing checksum helpers in the loop:
bash python3 .github/scripts/rusty_v8_bazel.py update-module-bazel python3 .github/scripts/rusty_v8_bazel.py check-module-bazel python3 -m unittest discover -s .github/scripts -p test_rusty_v8_bazel.pyValidate the release-candidate path before broadening the work:
- Prefer checking the
v8-canaryCI result for the candidate branch or PR when one exists, using GitHub check tooling orghas appropriate. - If CI is unavailable or the user asked for a local-only check, run the closest local validation that is practical for the changed surface and say explicitly that it is a local substitute, not the full hosted canary.
- Prefer checking the
If the canary path passes, stop there. Summarize the result and encourage the user to commit the candidate changes or proceed with the release flow they requested. Do not publish tags, releases, or pushes unless the user asked.
Show full SKILL.md (203 more words)Show less
Failure Path
Enter this path only when the canary or local build path fails.
- Capture the failing target, workflow job, and first actionable error.
- Compare the currently pinned version with the target version at the relevant
upstream tag or SHA. Inspect both:
denoland/rusty_v8- upstream V8 source at the target Bazel-pinned version
- Track build-relevant deltas rather than broad source churn:
- generated binding layout changes
- archive or asset naming changes
- GN/Bazel target changes
- custom libc++ / libc++abi / llvm-libc inputs
- sandbox or pointer-compression feature relationships
- patch hunks in
patches/that no longer apply or no longer match upstream
- Trace each failing delta back into Codex's build graph:
MODULE.bazelthird_party/v8/BUILD.bazel.github/scripts/rusty_v8_bazel.py.github/workflows/v8-canary.yml.github/workflows/rusty-v8-release.yml
- Update only the pieces required to restore the target version's build and artifact contract. Keep patch explanations and doc changes close to the affected files.
- Re-run the focused validation. If it becomes green, return to the normal workflow and stop with a concise summary plus the remaining release step.
Reporting
- Say whether validation came from hosted
v8-canaryor from a local substitute. - Distinguish "version bump complete" from "release published".
- When blocked, report the upstream delta that matters, the Codex file it hits, and the next concrete fix to try.
© openinterpreter, Apache-2.0. 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 1 other file in .codex/skills/update-v8-version of openinterpreter/openinterpreter.
- SKILL.md
- agents/openai.yaml
Open the folder on GitHubat commit cc054cf
Used in 2 other repositories
We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 2 other GitHub owners. This page covers the copy in openinterpreter/openinterpreter, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Update V8 Version 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 |
|---|---|---|---|---|---|---|
| Update V8 Version this skillopeninterpreter/openinterpreter | 69k | 2 repos | ~845 | Automated safety check: Pass | Apache-2.0 | |
| Uv WorkflowAedelon/claude-code-blueprint | 120 | — | ~1.2k | Automated safety check: Notes | Custom licence | |
| Universal Project Release WorkflowJimLiu/baoyu-skills | 26k | — | ~4.9k | Automated safety check: Pass | MIT | |
| CI/CD Failure Troubleshootingruby-git/ruby-git | 1.8k | — | ~1.9k | Automated safety check: Pass | MIT | |
| GitHub Actions Failure Analysisykdojo/claude-code-tips | 10k | — | ~639 | Automated safety check: Pass | Custom licence | |
| Sicurezza GitHubccplugins/awesome-claude-code-plugins | 967 | — | ~486 | Automated safety check: Notes | Apache-2.0 |
Similar skills
Universal Project Release Workflow
JimLiu/baoyu-skills
Detects a project's version file and changelog format, then runs a release: bumping the version, writing release notes and creating GitHub releases, including backfill.
CI/CD Failure Troubleshooting
ruby-git/ruby-git
Diagnoses and fixes failing GitHub Actions runs by identifying the failure, fetching only the relevant logs, finding the root cause and reproducing it locally.
GitHub Actions Failure Analysis
ykdojo/claude-code-tips
Investigates a failed GitHub Actions run from its URL: pinpoints the real failure, checks the job's history for flakiness, and finds the breaking commit and any existing fix PR.
Sicurezza GitHub
ccplugins/awesome-claude-code-plugins
Aggiunge alle repository GitHub dei siti workflow di sicurezza automatici - scansione dipendenze vulnerabili, ricerca di segreti/chiavi nel codice, analisi statica CodeQL e Dependabot.
CI Triage
andymai/brepjs
This skill should be used when a brepjs GitHub Actions job is red or behaving oddly on github.com (a remote CI run, not a local pre-commit/pre-push hook) — "CI failed", "ci-pass is failing", "npm ci…
More from openinterpreter/openinterpreter
All 10 skills in this repoPR Babysitter
openinterpreter/openinterpreter
Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.
Pull Request Title and Body Writer
openinterpreter/openinterpreter
Rewrites the title and body of one or more pull requests with gh, leading with why the change was made, then what changed, and describing only the net result.
Remote Executor Integration Tests
openinterpreter/openinterpreter
Explains how to run agent integration tests against remote executors, using Docker for Linux or Wine for Windows, and how to opt tests in or skip them.
Rust Path Types
openinterpreter/openinterpreter
Rules for choosing Rust types for filesystem paths in new Codex code, covering protocol types, internal use and model tool arguments.
Pull Request Code Review Orchestrator
openinterpreter/openinterpreter
Run a final code review on a pull request
Codex TUI Testing
openinterpreter/openinterpreter
Guide for testing Codex TUI interactively
Related
Categories
Questions about Update V8 Version
What does Update V8 Version do?
Bumps the pinned v8 and rusty_v8 versions in Codex, validates the release-candidate path with the v8-canary check, and traces failures to upstream build changes. bazel, the README and, when prebuilt inputs change, the matching rusty_v8 sha256 manifest.py update and check the module file, and a unit test file covers them.
When should I use Update V8 Version?
Update V8 Version fits situations like: bumping the pinned V8 or rusty_v8 version in Codex; checking the v8-canary result for a release candidate; diagnosing why a V8 version update no longer builds.
How do I install Update V8 Version in Claude Code?
Run `npx skills add openinterpreter/openinterpreter --skill update-v8-version -a claude-code`. Or copy the skill folder (.codex/skills/update-v8-version in openinterpreter/openinterpreter) into .claude/skills/update-v8-version in your project. Claude Code loads it when a task matches its description.
How do I install Update V8 Version in Codex?
Run `npx skills add openinterpreter/openinterpreter --skill update-v8-version -a codex`. Or copy the skill folder (.codex/skills/update-v8-version in openinterpreter/openinterpreter) into .agents/skills/update-v8-version in your project. Codex loads it when a task matches its description.
Can I use Update V8 Version 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 openinterpreter/openinterpreter --skill update-v8-version -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/update-v8-version, .gemini/skills/update-v8-version, .github/skills/update-v8-version and .opencode/skills/update-v8-version in your project.
What does Update V8 Version need to run?
Going by SKILL.md and its folder, Update V8 Version needs the command-line tools its instructions call (python3). Our summary lists: A checkout of the Codex repository; Python 3 for the checksum helper scripts; GitHub CLI (`gh`) or other GitHub check tooling.
Does Update V8 Version 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 Update V8 Version 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 Update V8 Version use?
Update V8 Version is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Update V8 Version use?
About 845 tokens (SKILL.md is roughly 3.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 Update V8 Version?
Skills that share tags, products or a category with Update V8 Version: Uv Workflow (Aedelon/claude-code-blueprint, 120 stars), Universal Project Release Workflow (JimLiu/baoyu-skills, 26k stars), CI/CD Failure Troubleshooting (ruby-git/ruby-git, 1.8k stars) and GitHub Actions Failure Analysis (ykdojo/claude-code-tips, 10k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Update V8 Version?
openinterpreter (a GitHub organization) maintains it in openinterpreter/openinterpreter, which has 68,517 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on October 7, 2026.
Source: openinterpreter/openinterpreter on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.