CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

rstudio-run-playwright-tests

How to run RStudio Playwright tests in Desktop and Server modes. Use this skill whenever the user asks to run, execute, or launch Playwright tests against RStudio - whether on Desktop (local) or Server (remote). Also use when the user asks about the test command, environment variables, or how to point tests at a server URL.

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

93%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

Exemplary SKILL.md body: dense repo-specific operational knowledge delivered as exact commands, a clear run-mode protocol, and disciplined deferral of detail to a single well-signaled README. The only gap is the absence of explicit build-verification checkpoints in the dev-mode prerequisite sequence.

DimensionReasoningScore

Conciseness

Lean and imperative throughout — the four-mode table, the numbered dev-build prerequisites, and the worktree/symlink caveats all convey facts Claude could not infer, with zero padding or explanation of known concepts (e.g., no "what is Playwright" prose).

5 / 5

Actionability

Fully executable guidance: exact npm scripts per mode ("npm run test:desktop -- tests/path/to/test.test.ts"), build prerequisites as copy-paste commands ("cmake --build build", "(cd src/gwt && ant draft)"), and a concrete profiling procedure (--trace on, pairing before/after events by callId) with a README pointer to a ready-to-run parser.

5 / 5

Workflow Clarity

The run protocol is clearly sequenced (mode pick with platform filtering and option ordering, run immediately, re-run without re-asking, re-prompt only on mode switch) and prerequisites are numbered, but there are no explicit validation checkpoints for the build steps (e.g., nothing confirms the cmake/GWT build succeeded before running tests). Matches the 4 anchor; not 5 for the missing checkpoints, clearly above 3 since the sequence is coherent and test pass/fail itself provides feedback.

4 / 5

Progressive Disclosure

A short, well-sectioned overview that defers setup, env vars, sandboxing, and the full profiling recipe to a single one-level-deep reference (e2e/rstudio/README.md), clearly signaled and even named by section ("the 'Profiling a slow test' section"). No nested references or inline bloat.

5 / 5

Total

19

/

20

Passed

Description

95%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A model description: concrete capability statement, explicit dual "Use when..." trigger clauses with synonym coverage, and a tightly scoped niche. It uses third-person/infinitive voice throughout with no fluff or over-claims.

DimensionReasoningScore

Specificity

"How to run RStudio Playwright tests in Desktop and Server modes" plus "test command, environment variables, or how to point tests at a server URL" names several concrete, differentiated capabilities with only minor gaps (dev-build variants not named). Not a 5: it centers on one action (running tests) with mode/config facets rather than a list of multiple distinct actions like extract/fill/merge.

4 / 5

Completeness

Explicitly answers what ("How to run RStudio Playwright tests in Desktop and Server modes") and when ("Use this skill whenever the user asks to run, execute, or launch Playwright tests against RStudio... Also use when the user asks about the test command...") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural user phrasing is comprehensively covered with synonyms — "run, execute, or launch" — plus "Playwright tests", "RStudio", "Desktop (local)", "Server (remote)", "test command", "environment variables", and "server URL". File extensions are not applicable to this domain.

5 / 5

Distinctiveness Conflict Risk

Clear niche — RStudio Playwright end-to-end tests — with distinct, specific triggers; minimal risk of firing for unrelated test-running or RStudio tasks.

5 / 5

Total

19

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

Repository

rstudio/rstudio

Path

.claude/skills/rstudio-run-playwright-tests/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.