playwright-devops
microsoft/playwright/.claude/skills/playwright-devops/SKILL.md
DevOps workflows for Playwright - CI failure analysis, workflow debugging, and release operations.
No other project uses it yet
Skills real projects publish on GitHub, most starred first. Each one says what it will make an agent do before you copy it.
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
microsoft/playwright/.claude/skills/playwright-devops/SKILL.md
DevOps workflows for Playwright - CI failure analysis, workflow debugging, and release operations.
No other project uses it yet
microsoft/playwright/.claude/skills/playwright-dev/SKILL.md
Explains how to develop Playwright - add APIs, MCP tools, CLI commands, and vendor dependencies.
1 project uses a version of this
microsoft/playwright/.claude/skills/playwright-release-notes/SKILL.md
Write the release notes for a Playwright release - the Node.js notes in docs/src/release-notes-js.md together with the Python, Java and .NET translations, and the GitHub markdown for each language's release. Use when asked to write, translate or publish release notes.
No other project uses it yet
microsoft/playwright/.claude/skills/playwright-test-results/SKILL.md
Query Playwright CI test results from the aggregated DuckDB database. Answers questions about flaky tests, failure rates, slow tests, and per-run/SHA/PR results without hunting through GitHub artifacts.
No other project uses it yet
microsoft/playwright/.claude/skills/playwright-triage/SKILL.md
Triage and fix one microsoft/playwright issue, or do a maintainer's task, unattended inside the Issue triage GitHub Actions workflow (.github/workflows/triage.yml), which a needs-triage, needs-triage-mac or needs-triage-win label starts, or a maintainer starts by hand with an issue, a task or both. Reproduces the issue on the runner, then leaves a verified fix proposal for the workflow to open as a draft PR, a test that covers a scenario that did not reproduce, an investigation note for it to post on the issue, or a browser bug report for it to file in microsoft/playwright-browsers or for a maintainer to file at crbug.com. Only for that workflow.
5 projects use a version of this
microsoft/playwright/packages/playwright-core/src/tools/skills/playwright-cli/SKILL.md
Automate browser interactions, test web pages and work with Playwright tests.
Often used withfabric-sdkecosystem-referencefractal-delegation
microsoft/playwright/packages/playwright-core/src/tools/skills/playwright-component-testing/SKILL.md
Set up component testing with Playwright using a story gallery — scaffold stories and a gallery dev page driven by the built-in mount fixture, no dedicated component-testing runtime. Use when asked to test React or Vue components in isolation with Playwright, or to migrate off @playwright/experimental-ct-react / -vue.
3 projects use a version of this
microsoft/playwright/packages/playwright-core/src/tools/skills/playwright-trace/SKILL.md
Inspect Playwright trace files from the command line — list actions, view requests, console, errors, snapshots and screenshots.
Surging+11 stars this week
5 projects use a version of this
modelcontextprotocol/servers/.claude/skills/board-ops/SKILL.md
gh recipes for the Servers V2 project board (#43): add an issue's card, move its Status, set or change its Priority, delete a card, and recover from a deleted single-select option. Use when moving a card between columns; when setting Status or Priority; when an option ID is rejected; before editing a board field's options; or when cards lost their Status or Priority.
Steady2 mentions in 2 weeks
3 projects use a version of this
modelcontextprotocol/servers/.claude/skills/client-smoke/SKILL.md
Drive a locally built server with a real client: the Inspector CLI (scripted), the Inspector web UI (through Playwright) and an LLM client. Use when smoke-testing a server change; when calling a tool, reading a resource or getting a prompt from the command line; when choosing a protocol era; or when the Inspector CLI will not connect to, or misreads, a server command.
Steady2 mentions in 2 weeks
No other project uses it yet
modelcontextprotocol/servers/.claude/skills/issue-create/SKILL.md
Create a tracked issue in this repo end to end — duplicate check, v2 label, type label, server-scope label, milestone, board card, Status and Priority. Use when asked to file, create, open or raise an issue; when picking its labels or its milestone; when checking whether one already exists; or when work discovered mid-task needs an issue of its own.
Steady2 mentions in 2 weeks
9 projects use a version of this
modelcontextprotocol/servers/.claude/skills/issue-triage/SKILL.md
Triage this repo's inflow — sweep unboarded issues onto the Servers V2 board (#43) as Incoming, score Priority with the rubric and post the score, classify outside PRs and spam (server listings, new servers, duplicates, no-ops) and close them with their canned comments, and run the board audit. Use for \"triage new issues\" or \"triage the PRs\"; when scoring an issue's Priority; when answering or closing an outside PR; or when auditing the board for drift.
Steady2 mentions in 2 weeks
63 projects use a version of this
modelcontextprotocol/servers/.claude/skills/local-dev/SKILL.md
Install, build and run a server from this checkout. Use when starting a server locally over stdio, SSE or Streamable HTTP; when pointing npx, uvx or an MCP client config at the local build; when a running server still shows old code, or dist is missing; when setting up a git worktree; or when adding an overrides pin.
Steady2 mentions in 2 weeks
7 projects use a version of this
modelcontextprotocol/servers/.claude/skills/pre-push-gate/SKILL.md
Run this repo's pre-push gate and fix it when it goes red. Use when npm run local:gate fails or a stage of it does (verify:install-fresh, a root guard, lint, typecheck, ruff, pyright, pytest, verify:skills:cli, the boot smoke); when the gate says it is waiting on the gate lease; or when checking whether a gate run really passed.
Steady2 mentions in 2 weeks
1 project uses a version of this
modelcontextprotocol/servers/.claude/skills/pr-flow/SKILL.md
Take an issue through to a PR in this repo and close it out after merge. Use when asked to open, create or submit a PR; when naming a branch; when signing off commits or repairing a missing Signed-off-by; when recording client evidence for a PR; when requesting a Copilot review, answering its comments or deciding whether to run another round; or when closing out after a merge.
Steady2 mentions in 2 weeks
3 projects use a version of this
modelcontextprotocol/servers/.claude/skills/project-structure/SKILL.md
Find where code lives in this repo's seven servers and decide where a new file goes. Use when choosing the file or directory for a new tool, resource, prompt, transport, helper module, command-line flag or root script; when a server's layout is unclear; or when asking whether code belongs in a server's entry file or a module of its own.
Steady2 mentions in 2 weeks
21 projects use a version of this
modelcontextprotocol/servers/.claude/skills/release/SKILL.md
Cut a milestone release: the release issue, the preparation PRs on v2/main (audit, changesets Version Packages, Python CalVer), the pure v2/main to main merge PR with its release ledger, then the GitHub Release a maintainer publishes.
Steady2 mentions in 2 weeks
196 projects use a version of this
Often used withcreate-agent-adapterdocumentation-consistency
modelcontextprotocol/servers/.claude/skills/security-advisory/SKILL.md
Take a privately reported vulnerability through this repo's security advisory flow: board it as a draft card, check whether the code is this repo's server or the SDK underneath, accept or reject, fix it in the private fork, release, publish, then turn the card into public tracking. Use when a vulnerability is reported privately; when deciding whether an advisory is ours to fix or belongs to an SDK; when looking up or creating its private fork; when answering a reporter; or when a GHSA-titled board card needs handling.
Steady2 mentions in 2 weeks
4 projects use a version of this
modelcontextprotocol/servers/.claude/skills/testing/SKILL.md
Write, place and run tests for a server in this repo. Use when choosing between driving the server through an MCP client and calling its functions directly; when writing a protocol-level test for a TypeScript or Python server; when choosing the command that runs one suite or a coverage report; or when a test is skipped or passes against a stale build.
Steady2 mentions in 2 weeks
194 projects use a version of this
Often used withbundle-dependency-prsupdate-library-template
astral-sh/uv/.codex/skills/load-github-action-thread/SKILL.md
When given an issue instead of a run, find the related issue-triage run first. Resolve the issue title and number, then match the run display title: Use the newest matching run. An issue-triage run can contain both the triage and bug-reproduction threads. Also check for directly dispatched bug-reproduction runs; their display title does not include the issue title. If the issue title changed or a run was manually dispatched, list recent candidates and confirm them from their logs: When given…
Steady2 mentions in 2 weeks
No other project uses it yet
A folder with a SKILL.md file: a name, a description of when to use it, and instructions. Claude loads a skill only when the task matches its description.
Copy the folder into your project's .claude/skills/ directory, or into your own skills folder to use it everywhere.
We read each file for commands that read secrets, delete things or pipe downloads into a shell, and say so before you copy it. No warning is not a promise that a file is safe.
Open a skill to see its discussion. Reports from people and their agents are coming.