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

RStudio Playwright Test Runner

by rstudio in rstudio/rstudio

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.

Custom licenceAuto-check passedTesting & QA

Install RStudio Playwright Test Runner

skills CLI
$ npx skills add rstudio/rstudio --skill rstudio-run-playwright-tests -a claude-code

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

GitHub CLI
$ gh skill install rstudio/rstudio rstudio-run-playwright-tests --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-run-playwright-tests .claude/skills/rstudio-run-playwright-tests && 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-run-playwright-tests
GitHub stars
5.1k
Token cost
~801 tokens
SKILL.md length
394 words
Files
1
Skills in repo
7
Repo updated
First seen
Licence
Custom licence

At a glance

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.

  • Works in 3 steps: cmake --build build -- C++ session → (cd src/gwt && ant draft) -- GWT… → (cd src/node/desktop && npm ci) --…
  • Running one RStudio Playwright test file against the desktop app
  • SKILL.md covers The four run modes, Test running protocol and Profiling a slow test
  • Calls npm, cmake and npx

What it does

The tests live under `e2e/rstudio/`, and the skill covers four ways to run them: an installed desktop app, a dev desktop build, an installed server and a dev server build. Each has its own `npm run test:*` script, and a test file path or Playwright flags go after the script name to run one file or filter by test name. The agent prefers the npm scripts over calling `npx playwright test` directly.

Before the first run in a conversation the agent asks which mode you want, leaving out modes your platform cannot run, and afterwards it re-runs without asking again unless you switch modes. The dev desktop mode needs a C++ session build, a GWT transpile and Electron dependencies, with a bootstrap script for secondary worktrees. When a test passes but runs slowly, the skill suggests a rerun with `--trace on` and reading per-action timing from the trace.

When your agent uses it

  • Running one RStudio Playwright test file against the desktop app
  • Pointing the end-to-end tests at an RStudio Server build
  • Finding out why a passing Playwright test takes too long

Example prompts

  • “Run the RStudio Playwright suite in installed desktop mode.”
  • “Run only the tests whose name contains 'autocomplete' against the dev server build.”
  • “This Playwright test passes but is slow. Trace it and show me which actions take the time.”

Requirements

  • npm and the RStudio `e2e/rstudio/` test project
  • An RStudio desktop or server build to test
  • For the dev desktop mode: CMake, Ant and a GWT build

Workflow steps

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

  1. cmake --build build -- C++ session
  2. (cd src/gwt && ant draft) -- GWT transpile (2-5 min; rerun after Java edits)
  3. (cd src/node/desktop && npm ci) -- Electron deps

What it can do on your machine

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

    • npm
    • cmake
    • npx

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

  • Network

    No URLs in SKILL.md. Its commands use npm and npx, 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 Playwright Test Runner loads about 801 tokens when it runs. Until then it costs about 89 tokens; SKILL.md has 394 words of instructions outside code blocks.

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

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 394 words (~801 tokens).

“Run from e2e/rstudio/. Setup, env vars, tags, sandbox, external-server config, and the cross-env / dotenv helpers all live in e2e/rstudio/README.md -- open it when you need any of that.”

— opening of SKILL.md by rstudio, Custom licence
name
rstudio-run-playwright-tests

Read the full SKILL.md on GitHub

Files

Just SKILL.md in .claude/skills/rstudio-run-playwright-tests of rstudio/rstudio.

Open the folder on GitHubat commit ed04cb7

Compare with similar skills

RStudio Playwright Test Runner 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 Playwright Test Runner compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
RStudio Playwright Test Runner this skillrstudio/rstudio5.1k—~801Automated safety check: PassCustom licence
PlaywrightKiln-AI/Kiln5.2k—~1.3kAutomated safety check: PassCustom licence
Proxy Setupasmyshlyaev177/test-proxy-recorder112—~4.3kAutomated safety check: PassMIT
Dev Webtestclassmethod/tsumiki974—~4.2kAutomated safety check: PassMIT
Building Farm From Sourcefarm-fe/farm5.6k—~857Automated safety check: PassMIT
Nix Playwrightsrid/emanote963—~557Automated safety check: PassCustom licence

Similar skills

  • Playwright

    Kiln-AI/Kiln

    Look at Kiln's UI in a real browser, and run its end-to-end tests.

    5.2k GitHub stars~1.3k tokensUpdated yesterday
    Testing & QAAuto-check passed

  • Proxy Setup

    asmyshlyaev177/test-proxy-recorder

    Set up test-proxy-recorder for any Playwright project. An agent skill from asmyshlyaev177/test-proxy-recorder.

    112 GitHub stars~4.3k tokensUpdated 5 days ago
    Testing & QAAuto-check passed

  • Dev Webtest

    classmethod/tsumiki

    This skill should be used when the user asks to "dev-webtest", "Webテスト", "画面の動作確認", "E2Eテスト", "web test", "visual check", "モンキーテスト", "アクセシビリティチェック", "レスポンシブテスト", "フォームテスト".

    974 GitHub stars~4.2k tokensUpdated 2 mo ago
    Testing & QAAuto-check passed

  • Building Farm From Source

    farm-fe/farm

    A skill your agent uses when building Farm locally from source, native bindings or Rust plugin artifacts are missing, or an example/E2E needs local core and plugin artifacts.

    5.6k GitHub stars~857 tokensUpdated 16 days ago
    Testing & QAAuto-check passed

  • Nix Playwright

    srid/emanote

    Use this when adding Nix-based local runs for an existing Playwright e2e suite.

    963 GitHub stars~557 tokensUpdated 2 mo ago
    Testing & QAAuto-check passed

  • Pw Init

    alirezarezvani/claude-skills

    Set up Playwright in a project. An agent skill from alirezarezvani/claude-skills.

    28k GitHub starsUsed in 1 repo~1.2k tokens
    Testing & QAAuto-check passed

More from rstudio/rstudio

  • RStudio Selenium to Playwright Migration

    rstudio/rstudio

    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 yesterday
    Auto-check passed

  • RStudio Copilot Language Server Updater

    rstudio/rstudio

    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 yesterday
    Auto-check passed

  • RStudio Electron Version Update

    rstudio/rstudio

    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 yesterday
    Auto-check passed

  • RStudio Node.js Version Update

    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.

    5.1k GitHub stars~2.7k tokensUpdated yesterday
    Auto-check passed

  • Update Quarto in RStudio

    rstudio/rstudio

    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 yesterday
    Auto-check passed

  • RStudio Playwright Test Patterns

    rstudio/rstudio

    Gotchas and conventions for writing, reviewing and migrating RStudio's TypeScript Playwright tests under e2e/rstudio, beyond what the README covers.

    5.1k GitHub stars~3.9k tokensUpdated yesterday
    Auto-check passed

Works with

Categories

Questions about RStudio Playwright Test Runner

What does RStudio Playwright Test Runner do?

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. The tests live under `e2e/rstudio/`, and the skill covers four ways to run them: an installed desktop app, a dev desktop build, an installed server and a dev server build. Each has its own `npm run test:*` script, and a test file path or Playwright flags go after the script name to run one file or filter by test name.

When should I use RStudio Playwright Test Runner?

RStudio Playwright Test Runner fits situations like: running one RStudio Playwright test file against the desktop app; pointing the end-to-end tests at an RStudio Server build; finding out why a passing Playwright test takes too long.

How do I install RStudio Playwright Test Runner in Claude Code?

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

How do I install RStudio Playwright Test Runner in Codex?

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

Can I use RStudio Playwright Test Runner 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-run-playwright-tests -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-run-playwright-tests, .gemini/skills/rstudio-run-playwright-tests, .github/skills/rstudio-run-playwright-tests and .opencode/skills/rstudio-run-playwright-tests in your project.

What does RStudio Playwright Test Runner need to run?

Going by SKILL.md and its folder, RStudio Playwright Test Runner needs the command-line tools its instructions call (npm, cmake and npx). Our summary lists: npm and the RStudio `e2e/rstudio/` test project; An RStudio desktop or server build to test; For the dev desktop mode: CMake, Ant and a GWT build.

Does RStudio Playwright Test Runner access the network?

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

Is RStudio Playwright Test Runner 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 Playwright Test Runner use?

RStudio Playwright Test Runner 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 Playwright Test Runner use?

About 801 tokens (SKILL.md is roughly 3.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 RStudio Playwright Test Runner?

Skills that share tags, products or a category with RStudio Playwright Test Runner: Playwright (Kiln-AI/Kiln, 5.2k stars), Proxy Setup (asmyshlyaev177/test-proxy-recorder, 112 stars), Dev Webtest (classmethod/tsumiki, 974 stars) and Building Farm From Source (farm-fe/farm, 5.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains RStudio Playwright Test Runner?

rstudio (a GitHub organization) maintains it in rstudio/rstudio, which has 5,081 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 8, 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.