New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Official agent skill

Run Smoke Tests

by cursor in cursor/plugins

Run Playwright smoke tests, debug failures, and verify fixes

OfficialNo licenceAuto-check passedTesting & QA

Install Run Smoke Tests

skills CLI
$ npx skills add cursor/plugins --skill run-smoke-tests -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install cursor/plugins run-smoke-tests --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/cursor/plugins.git skills-src && mkdir -p .claude/skills && cp -r skills-src/cursor-team-kit/skills/run-smoke-tests .claude/skills/run-smoke-tests && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
run-smoke-tests
GitHub stars
10k
Used in
1 other repo
Token cost
~242 tokens
SKILL.md length
90 words
Files
1
Skills in repo
99
Repo updated
First seen
Licence
None found

At a glance

Run Playwright smoke tests, debug failures, and verify fixes

  • Works in 4 steps: Build prerequisites for the target app. → Run the relevant smoke suite or a… → If failing, inspect traces/logs and… → …
  • Tasks that involve QA and bug reports
  • SKILL.md covers Trigger, Workflow, Example Commands and Guardrails, plus 1 more section
  • Calls npm

What it does

Run Smoke Tests is an agent skill from cursor/plugins, published by the product's own GitHub organization. Run Playwright smoke tests, debug failures, and verify fixes

Its SKILL.md is about 240 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Testing & QA, covering QA and bug reports. It works with Playwright. The repository describes itself as: Cursor plugin specification and official plugins.

When your agent uses it

  • Tasks that involve QA and bug reports

Example prompts

  • “/run-smoke-tests”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Build prerequisites for the target app.
  2. Run the relevant smoke suite or a focused test file.
  3. If failing, inspect traces/logs and isolate the root cause.
  4. Apply a minimal fix and rerun until stable.

What it can do on your machine

Read from SKILL.md and the folder at commit ccb5507. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • npm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use npm, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Run Smoke Tests loads about 242 tokens when it runs. Until then it costs about 19 tokens; SKILL.md has 90 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~19
When it runs · the whole SKILL.md, loaded when a task matches
~242

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

Without a licence we can't republish the file, so here is its outline and opening line. It has 90 words (~242 tokens).

“Need end-to-end smoke verification before or after changes.”

— opening of SKILL.md by cursor
name
run-smoke-tests

Read the full SKILL.md on GitHub

Files

Just SKILL.md in cursor-team-kit/skills/run-smoke-tests of cursor/plugins.

Open the folder on GitHubat commit ccb5507

Used in 1 other repository

We found 4 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in cursor/plugins, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Run Smoke Tests next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Run Smoke Tests compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Run Smoke Tests this skillcursor/plugins10k1 repos~242Automated safety check: PassNone
Diagnose Playwright Failure as Product Bugappsmithorg/appsmith41k—~1.5kAutomated safety check: PassApache-2.0
Evidence-Driven Testingmichaelshimeles/skills1.3k1 repos~3.9kAutomated safety check: PassNone
Verify Omnigent End-to-Endomnigent-ai/omnigent11k—~1.6kAutomated safety check: PassApache-2.0
Hands On Testktnyt/cclsp675—~1.7kAutomated safety check: PassMIT
Glance TestDebugBase/glance156—~827Automated safety check: PassMIT

Similar skills

  • Diagnose Playwright Failure as Product Bug

    appsmithorg/appsmith

    Investigates a stubbornly failing Playwright test as a possible product bug, using error output, screenshots, traces and server code, and writes a structured bug report.

    41k GitHub stars~1.5k tokensUpdated today
    Testing & QAAuto-check passed

  • Evidence-Driven Testing

    michaelshimeles/skills

    Records an annotated screen recording of the agent testing an app hands-on, then posts the video and a results summary to the PR and tracker issue.

    1.3k GitHub starsUsed in 1 repo~3.9k tokens
    Testing & QAAuto-check passed

  • Verify Omnigent End-to-End

    omnigent-ai/omnigent

    Spins up an isolated Omnigent server, runner and mock model to prove a user-facing behavior or bug fix with recorded evidence instead of reasoning from code.

    11k GitHub stars~1.6k tokensUpdated today
    Testing & QAAuto-check passed

  • Hands On Test

    ktnyt/cclsp

    Performs manual hands-on testing of a web application using playwright-cli.

    675 GitHub stars~1.7k tokensUpdated 7 mo ago
    Testing & QAAuto-check passed

  • Glance Test

    DebugBase/glance

    Run E2E browser tests on any web application using Glance MCP.

    156 GitHub stars~827 tokensUpdated 5 mo ago
    Testing & QAAuto-check passed

  • Electron App Screenshot

    keybase/client

    Takes a screenshot of a running Electron desktop app through playwright-cli over remote debugging, shrinks it and shows it so you can check the UI visually.

    9.3k GitHub stars~476 tokensUpdated yesterday
    Testing & QAAuto-check passed

More from cursor/plugins

All 99 skills in this repo

  • Show Me Your Work Decision Log

    cursor/plugins

    Official

    Keeps a TSV decision log for long or unattended agent runs, one row per decision with what, why, evidence and result, so a reviewer can check the work later.

    10k GitHub starsUsed in 9 repos~1.6k tokens
    Auto-check passed

  • Code Design Rationale Investigator

    cursor/plugins

    Official

    Digs into why code is shaped the way it is by checking git history, pull requests and connected tools in parallel, then reporting a cited read on the tradeoffs.

    10k GitHub starsUsed in 9 repos~2.6k tokens
    Auto-check passed

  • Reflect on Session Learnings

    cursor/plugins

    Official

    Starts three parallel reviewer subagents over the current conversation transcript, then turns their findings into concrete edits to existing skills.

    10k GitHub starsUsed in 5 repos~1.2k tokens
    Auto-check passed

  • Technical Writing Standard

    cursor/plugins

    Official

    Applies four layers of technical-writing rules to docs, RFCs, readmes, PR descriptions and commit messages so a tired engineer follows them on the first read.

    10k GitHub starsUsed in 10 repos~2.4k tokens
    Auto-check passed

  • Advisor Mode

    cursor/plugins

    Official

    Adds a second, stronger model that the main agent consults before major decisions, when stuck and before finishing, controlled by /advisor commands.

    10k GitHub stars~2.6k tokensUpdated today
    Auto-check: notes

  • Make PR Easy To Review

    cursor/plugins

    Official

    Prepare PRs for review by cleaning noisy history, improving PR descriptions, and adding reviewer guidance without changing code behavior.

    10k GitHub starsUsed in 3 repos~569 tokens
    Auto-check passed

Works with

Categories

Questions about Run Smoke Tests

What does Run Smoke Tests do?

Run Playwright smoke tests, debug failures, and verify fixes. Run Smoke Tests is an agent skill from cursor/plugins, published by the product's own GitHub organization.

When should I use Run Smoke Tests?

Run Smoke Tests fits situations like: tasks that involve QA and bug reports.

How do I install Run Smoke Tests in Claude Code?

Run `npx skills add cursor/plugins --skill run-smoke-tests -a claude-code`. Or copy the skill folder (cursor-team-kit/skills/run-smoke-tests in cursor/plugins) into .claude/skills/run-smoke-tests in your project. Claude Code loads it when a task matches its description.

How do I install Run Smoke Tests in Codex?

Run `npx skills add cursor/plugins --skill run-smoke-tests -a codex`. Or copy the skill folder (cursor-team-kit/skills/run-smoke-tests in cursor/plugins) into .agents/skills/run-smoke-tests in your project. Codex loads it when a task matches its description.

Can I use Run Smoke Tests in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add cursor/plugins --skill run-smoke-tests -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/run-smoke-tests, .gemini/skills/run-smoke-tests, .github/skills/run-smoke-tests and .opencode/skills/run-smoke-tests in your project.

What does Run Smoke Tests need to run?

Going by SKILL.md and its folder, Run Smoke Tests needs the command-line tools its instructions call (npm).

Does Run Smoke Tests access the network?

SKILL.md contains no URLs. Its commands use npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Run Smoke Tests safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Run Smoke Tests use?

No licence was found for Run Smoke Tests or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.

How many tokens does Run Smoke Tests use?

About 242 tokens (SKILL.md is roughly 968 characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Run Smoke Tests?

Skills that share tags, products or a category with Run Smoke Tests: Diagnose Playwright Failure as Product Bug (appsmithorg/appsmith, 41k stars), Evidence-Driven Testing (michaelshimeles/skills, 1.3k stars), Verify Omnigent End-to-End (omnigent-ai/omnigent, 11k stars) and Hands On Test (ktnyt/cclsp, 675 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Run Smoke Tests?

cursor (a GitHub organization, an official publisher) maintains it in cursor/plugins, which has 10,278 GitHub stars. The repository holds 99 skills in this directory. The repository was last updated on October 8, 2026.

Source: cursor/plugins on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.