Agent skill

RStudio Node.js Version Update

by rstudio in rstudio/rstudio

Bumps the build-time and installed Node.js versions in the RStudio repository, uploads the binaries to S3, verifies the install and opens a PR.

Custom licenceAuto-check passedDevelopment

Install RStudio Node.js Version Update

skills CLI
$ npx skills add rstudio/rstudio --skill rstudio-update-nodejs -a claude-code

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

GitHub CLI
$ gh skill install rstudio/rstudio rstudio-update-nodejs --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/rstudio/rstudio.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/rstudio-update-nodejs .claude/skills/rstudio-update-nodejs && 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
rstudio-update-nodejs
GitHub stars
5.1k
Token cost
~2.7k tokens
SKILL.md length
1,137 words
Files
1
Skills in repo
8
Repo updated
First seen
Licence
Custom licence

At a glance

Bumps the build-time and installed Node.js versions in the RStudio repository, uploads the binaries to S3, verifies the install and opens a PR.

  • Works in 8 steps: Verify starting branch → Validate the version(s) → Check prerequisites → …
  • Updating the build-time Node.js version in the RStudio repository
  • SKILL.md covers Arguments and Steps
  • Calls git, bash and aws

What it does

RStudio pins two separate Node.js versions: the build-time one (`RSTUDIO_NODE_VERSION`), used to build Electron and GWT, and the installed one (`RSTUDIO_INSTALLED_NODE_VERSION`), a stripped-down binary shipped with the product and used by GitHub Copilot and Posit Assistant. You name one or both versions in X.Y.Z form. The agent first confirms it is on `main`, validates the version strings and checks prerequisites before touching any files.

Prerequisites are the `aws` and `wget` commands and working AWS credentials, since binaries are uploaded to S3, and the skill suggests `aws sso login` when credentials are missing. It then creates a feature branch named for the kind of update, changes the pinned versions, uploads, verifies the install and opens a PR. It is for macOS and Linux only, and the excerpt is cut off after the branch naming step.

When your agent uses it

  • Updating the build-time Node.js version in the RStudio repository
  • Updating the Node.js version that ships with RStudio
  • Updating both pinned Node.js versions in one go

Example prompts

  • “Update build node to 22.14.0.”
  • “Update installed node to 22.23.0 in the RStudio repo.”
  • “Update build node to 22.14.0 and installed node to 22.23.0.”

Requirements

  • The `aws` CLI with working AWS credentials
  • `wget`
  • macOS or Linux, starting from the `main` branch

Workflow steps

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

  1. Verify starting branch
  2. Validate the version(s)
  3. Check prerequisites
  4. Create a branch
  5. Update version strings
  6. Upload to S3
  7. Verify the install
  8. Commit and open a PR

What it can do on your machine

Read from SKILL.md and the folder at commit d051070. 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
    • bash
    • aws

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

  • Network

    No URLs in SKILL.md. Its commands use git and aws, which can reach the network depending on how they are called.

    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

RStudio Node.js Version Update loads about 2.7k tokens when it runs. Until then it costs about 79 tokens; SKILL.md has 1,137 words of instructions outside code blocks.

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

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

Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 1,137 words (~2,692 tokens).

“Updates the pinned Node.js version(s) across the RStudio codebase, uploads binaries to S3, verifies the install, and opens a PR.”

— opening of SKILL.md by rstudio, Custom licence
name
rstudio-update-nodejs

Read the full SKILL.md on GitHub

Files

Just SKILL.md in .claude/skills/rstudio-update-nodejs of rstudio/rstudio.

Open the folder on GitHubat commit d051070

Compare with similar skills

RStudio Node.js Version Update 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.

RStudio Node.js Version Update compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
RStudio Node.js Version Update this skillrstudio/rstudio5.1k—~2.7kAutomated safety check: PassCustom licence
Elastic Beanstalk Deploymentpr-pm/prpm122—~2.5kAutomated safety check: PassMIT
Aube Package Manager Helperaubepkg/aube2k—~1.1kAutomated safety check: WarnMIT
PR Reviewcdklabs/cdk-nextjs110—~2kAutomated safety check: PassApache-2.0
Dep Auditorlaolaoshiren/claude-code-skills-zh877—~895Automated safety check: PassMIT
Bun Runtime and Toolkitmweinbach/agent-coworker156—~2.2kAutomated safety check: NotesCustom licence

Similar skills

  • A skill your agent uses when deploying Node.js applications to AWS Elastic Beanstalk or troubleshooting deployment issues - provides dependency installation strategies, monorepo handling, and…

    122 GitHub stars~2.5k tokensUpdated today
    DevelopmentAuto-check passed
  • Manages Node.js dependencies, scripts and installs with aube, aubr and aubx, choosing the right command by its effect and preserving the project's existing lockfile and workspace format.

    2k GitHub stars~1.1k tokensUpdated today
    DevelopmentAuto-check: warnings
  • PR Review

    cdklabs/cdk-nextjs

    Review the current PR branch and fix the findings in rounds until reviews come back clean.

    110 GitHub stars~2k tokensUpdated today
    DevelopmentAuto-check passed
  • Dep Auditor

    laolaoshiren/claude-code-skills-zh

    审计 Node.js、Python、Go、Rust、JVM、Ruby 项目的依赖漏洞、版本健康度与许可证事实;当用户要求检查 package.json、lockfile、requirements、go.mod、Cargo.toml、pom.xml、Gemfile.lock,或生成不改依赖的中文审计报告时使用

    877 GitHub stars~895 tokensUpdated 2 days ago
    DevelopmentAuto-check passed
  • Bun Runtime and Toolkit

    mweinbach/agent-coworker

    Quick reference for using Bun to run TypeScript and JavaScript, install packages, bundle code, run tests and serve HTTP, with the key files and commands.

    156 GitHub stars~2.2k tokensUpdated today
    DevelopmentAuto-check: notes
  • Handsontable Node Script Conventions

    handsontable/handsontable

    Conventions for .mjs files in the Handsontable monorepo: native node: imports, top-level await, the tasks.json dispatcher and native modules instead of extra dependencies.

    22k GitHub stars~1.1k tokensUpdated today
    DevelopmentAuto-check passed

More from rstudio/rstudio

All 8 skills in this repo
  • Converts RStudio Python Selenium electron tests into TypeScript Playwright tests, checking each against a live RStudio before counting it as migrated.

    5.1k GitHub stars~3.6k tokensUpdated today
    Auto-check passed
  • Turns the current release's NEWS.md entries into the RStudio Desktop What's New page, picking only what Desktop users care about, then commits and opens a PR.

    5.1k GitHub stars~2k tokensUpdated today
    Auto-check passed
  • Runs RStudio's Playwright end-to-end tests against the desktop app or a server build with the project's npm scripts, asking you which mode to use first.

    5.1k GitHub stars~801 tokensUpdated today
    Auto-check passed
  • Advances RStudio's pinned copilot-language-server dependency to a specified release, then uploads it to S3, verifies the install, and opens a PR.

    5.1k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Bumps the pinned Electron version across the RStudio repository, updating NEWS.md, package.json, the lockfile and the allowScripts entry.

    5.1k GitHub stars~964 tokensUpdated today
    Auto-check passed
  • Bumps the pinned Quarto version across the RStudio repository, mirrors the release to the rstudio-buildtools S3 bucket, verifies it and opens a PR, on macOS and Linux.

    5.1k GitHub stars~2.8k tokensUpdated today
    Auto-check passed

Questions about RStudio Node.js Version Update

What does RStudio Node.js Version Update do?

Bumps the build-time and installed Node.js versions in the RStudio repository, uploads the binaries to S3, verifies the install and opens a PR. js versions: the build-time one (`RSTUDIO_NODE_VERSION`), used to build Electron and GWT, and the installed one (`RSTUDIO_INSTALLED_NODE_VERSION`), a stripped-down binary shipped with the product and used by GitHub Copilot and Posit Assistant.Z form.

When should I use RStudio Node.js Version Update?

RStudio Node.js Version Update fits situations like: updating the build-time Node.js version in the RStudio repository; updating the Node.js version that ships with RStudio; updating both pinned Node.js versions in one go.

How do I install RStudio Node.js Version Update in Claude Code?

Run `npx skills add rstudio/rstudio --skill rstudio-update-nodejs -a claude-code`. Or copy the skill folder (.claude/skills/rstudio-update-nodejs in rstudio/rstudio) into .claude/skills/rstudio-update-nodejs in your project. Claude Code loads it when a task matches its description.

How do I install RStudio Node.js Version Update in Codex?

Run `npx skills add rstudio/rstudio --skill rstudio-update-nodejs -a codex`. Or copy the skill folder (.claude/skills/rstudio-update-nodejs in rstudio/rstudio) into .agents/skills/rstudio-update-nodejs in your project. Codex loads it when a task matches its description.

Can I use RStudio Node.js Version Update 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 rstudio/rstudio --skill rstudio-update-nodejs -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/rstudio-update-nodejs, .gemini/skills/rstudio-update-nodejs, .github/skills/rstudio-update-nodejs and .opencode/skills/rstudio-update-nodejs in your project.

What does RStudio Node.js Version Update need to run?

Going by SKILL.md and its folder, RStudio Node.js Version Update needs the command-line tools its instructions call (git, bash and aws). Our summary lists: The `aws` CLI with working AWS credentials; `wget`; macOS or Linux, starting from the `main` branch.

Does RStudio Node.js Version Update access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is RStudio Node.js Version Update 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 RStudio Node.js Version Update use?

RStudio Node.js Version Update has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.

How many tokens does RStudio Node.js Version Update use?

About 2.7k tokens (SKILL.md is roughly 11k 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 RStudio Node.js Version Update?

Skills that share tags, products or a category with RStudio Node.js Version Update: Elastic Beanstalk Deployment (pr-pm/prpm, 122 stars), Aube Package Manager Helper (aubepkg/aube, 2k stars), PR Review (cdklabs/cdk-nextjs, 110 stars) and Dep Auditor (laolaoshiren/claude-code-skills-zh, 877 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains RStudio Node.js Version Update?

rstudio (a GitHub organization) maintains it in rstudio/rstudio, which has 5,081 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on October 6, 2026.

Source: rstudio/rstudio on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.