Skip to content
TrustedSkillsbeta
Back to all skills

Playwright Ci Caching

Checked
aaronontheweb·vlatest·testing·MIT

Speeds up Playwright CI runs by caching browser downloads and test artifacts, reducing setup time significantly.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add aaronontheweb/dotnet-skills --skill playwright-ci-caching -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

aaronontheweb

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned aaronontheweb/dotnet-skills at e426ed93a9.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
e426ed93a9
Manifest
skills/playwright-ci-caching/SKILL.md
Scanned
1 file, 212 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill significantly speeds up Playwright E2E testing in CI/CD pipelines by caching browser downloads and test artifacts. It avoids repeatedly downloading large browser binaries (approximately 400MB) on each build, reducing setup time from 1-2 minutes. The cache is automatically invalidated whenever the Playwright version changes, ensuring you always use compatible browsers.

When to use it

  • You're setting up CI/CD for a project using Playwright E2E tests.
  • Your build times are slow due to browser download overhead.
  • You want automatic cache invalidation when the Playwright version is updated.
  • You’re using GitHub Actions or Azure DevOps pipelines.

Key capabilities

  • Caches Playwright browsers based on operating system (Linux, macOS, Windows).
  • Extracts the Playwright version from Directory.Packages.props to use as a cache key.
  • Automatically invalidates the browser cache when the Playwright version changes.
  • Provides example configurations for GitHub Actions and Azure DevOps pipelines.

Example prompts

  • "Configure caching for my Playwright tests in GitHub Actions."
  • "How can I speed up my Azure DevOps builds with Playwright?"
  • "Set up browser caching for Playwright E2E testing."

Tips & gotchas

  • This skill requires a Directory.Packages.props file to determine the Playwright version.
  • The cache paths are OS-specific: ~/.cache/ms-playwright (Linux), ~/Library/Caches/ms-playwright (macOS), and %USERPROFILE%\AppData\Local\ms-playwright (Windows).
  • Ensure your CI/CD pipeline environment has the necessary permissions to write to the cache directory.