Ci

Skill up1/demo-api-testing-with-playwright-skill/.agents/skills/playwright-skill/ci

API testing with Playwright Skill

Install

npx -y skills add up1/demo-api-testing-with-playwright-skill --skill ci

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Production-ready CI/CD configurations for Playwright — GitHub Actions, GitLab CI, CircleCI, Azure DevOps, Jenkins, Docker, parallel sharding, reporting, code coverage, and global setup/teardown.

SKILL.md

2.1 KB, as published. Nobody here has run it

Playwright CI/CD

Ship reliable tests in every pipeline — CI-specific patterns for speed, stability, and actionable reports.

9 guides covering CI/CD setup, parallel execution, containerized runs, reporting, and infrastructure patterns for all major CI providers.

Golden Rules

retries: 2 in CI only — surface flakiness in pipelines, not locally
traces: 'on-first-retry' — capture rich debugging artifacts without slowing every run
Shard across runners — --shard=N/M splits tests evenly; scale horizontally, not vertically
Cache browser binaries — ~/.cache/ms-playwright keyed on Playwright version
Upload artifacts on failure — traces, screenshots, and HTML reports as CI artifacts
Use the official Docker image — mcr.microsoft.com/playwright:v* has all OS deps pre-installed
Global setup for auth — run login once in globalSetup, reuse storageState across workers
Fail fast, debug later — keep CI runs short; use trace viewer and HTML reports to investigate

Guide Index

CI Providers

Provider	Guide
GitHub Actions	ci-github-actions.md
GitLab CI	ci-gitlab.md
CircleCI / Azure DevOps / Jenkins	ci-other.md

Execution & Scaling

Topic	Guide
Parallel execution & sharding	parallel-and-sharding.md
Docker & containers	docker-and-containers.md
Multi-project config	projects-and-dependencies.md

Reporting & Setup

Topic	Guide
Reports & artifacts	reporting-and-artifacts.md
Code coverage	test-coverage.md
Global setup/teardown	global-setup-teardown.md

Gives 0 of the 12 instructions most containers cloud skills give

Counted across 607 of the 657 authors here whose files we hold, read 2026-08-06

run containers as a non-root userin 69 of 607, across 49 files
use multi-stage buildsin 52 of 607, across 41 files
use Promise.all for independent operationsin 47 of 607, across 13 files
import directly instead of barrel filesin 46 of 607, across 12 files
use ternary instead of AND for conditionalsin 45 of 607, across 12 files
use Set or Map for O(1) lookupsin 42 of 607, across 10 files
create a .dockerignore filein 41 of 607, across 31 files
Read individual rule files for detailsin 39 of 607, across 9 files
authenticate server actions like API routesin 35 of 607, across 7 files
use next/dynamic for heavy componentsin 34 of 607, across 9 files
use React.cache for per-request deduplicationin 34 of 607, across 10 files
copy dependency files before source codein 34 of 607, across 21 files

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.