Is write-e2e-cases safe to install?

SaferSkills independently audited write-e2e-cases (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.

CategoryWeightCategory scoreContribution

Securityprompt, exec, net, exfil, eval

35%

100

35.0 pts

Supply chainhash, typosquat, maintainer, lockfile

20%

100

20.0 pts

Maintenancestaleness, pinning, CI

15%

100

15.0 pts

TransparencySKILL.md, perms, README

15%

100

15.0 pts

Communityinstalls, verify, response

15%

100

15.0 pts

Findings & checks · 0 flagged

Securityscore 100 · 0 findings

✓—All security checks passedNo findings in this category for the latest scan.pass

Supply chainscore 100 · 0 findings

✓—All supply chain checks passedNo findings in this category for the latest scan.pass

Maintenancescore 100 · 0 findings

✓—All maintenance checks passedNo findings in this category for the latest scan.pass

Transparencyscore 100 · 0 findings

✓—All transparency checks passedNo findings in this category for the latest scan.pass

Communityscore 100 · 0 findings

✓—All community checks passedNo findings in this category for the latest scan.pass

The primary manifest — the file an agent reads to learn what this artifact does.

.agents/skills/write-e2e-cases/SKILL.md · 1 file

.agents/skills/write-e2e-cases/SKILL.md1.7 KB · Markdown

name: write-e2e-cases

description: Use when adding or updating Rsdoctor end-to-end tests in `e2e/cases/`, including new feature coverage, bug reproduction, and regression prevention.

Write E2E Cases

Rsdoctor E2E tests use Playwright and live under e2e/cases/. Each bundler has its own directory:

e2e/cases/doctor-rspack/ — tests using Rspack compilation
e2e/cases/doctor-rsbuild/ — tests using Rsbuild
e2e/cases/doctor-rspeedy/ — tests using Rspeedy

Steps

Review uncommitted git changes to define test scope and target behavior.

Read e2e/README.md and follow its conventions.

Use helpers from @scripts/test-helper (for example compileByRspack) to compile fixtures. Do not call bundler APIs directly.

Add Playwright test files under the appropriate e2e/cases/doctor-* directory, following existing patterns.

Test fixtures (source files, loaders, configs) go in fixtures/ subdirectories inside each case directory.

Keep assertions focused and readable; avoid redundant setup and checks.

Run pnpm e2e from the repository root to validate.

Case Structure

Each test file creates an Rsdoctor plugin instance (e.g., createRsdoctorPlugin from a local test-utils.ts), compiles a fixture via compileByRspack, and asserts on the SDK store data.
Fixtures are plain JS/TS files and loaders in fixtures/ — not full application directories.
Use @rsdoctor/core/plugins for getSDK / setSDK when inspecting analysis results.

Constraints

If tests can pass only after source-code changes, do not change source code directly. Explain the required source change and ask the user before proceeding.

write-e2e-cases— agent skill

Is write-e2e-cases safe to install?

Write E2E Cases

Steps

Case Structure

Constraints

Audit the pieces. Scan the whole. Decide.