run-smoke-tests
Inspect an unfamiliar repository, interpret a broad Markdown user journey at runtime, operate the real product through its supported web, API, CLI, desktop, or mobile surface, and produce an auditable pass, fail, or blocked judgment with screenshots, logs, recordings, and a step timeline when available. Use when asked to run smoke tests, validate an end-to-end user journey, dogfood a product, test a release candidate, or execute a non-deterministic workflow that may include authentication or human checkpoints. Do not use as a substitute for deterministic unit, integration, or scenario tests.
npx skills add tamdogood/builder-essential-skills --skill run-smoke-tests --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Run Smoke Tests Execute a broad user journey against a real build and leave enough evidence for a person to audit the judgment. Understand the host project before starting the product or touching its state. ## Operating contract - Treat the Markdown as runtime instructions, not source to compile into code. - Test through a supported user-facing surface: web UI, API, CLI, desktop, mobile, or a documented combination. - Separate execution from repair. Do not edit the product, tests, or journey during a run. Finish the report before starting any requested fix. - Default to local, test, preview, or staging environments. Never mutate production, spend money, send real invitations, or change real user data without explicit authorization. - Make every pass or fail claim traceable to captured evidence. - Keep the first failed run. Do not erase evidence by retrying until green. ## Workflow ### 1. Pass the repository-understanding gate Read the nearest repository instructions, product README, runbook, contribution guide, manifests, launch scripts, existing smoke or end-to-end tests, and the smallest relevant product documentation. Search for auth setup, seed data, test accounts, feature fl
- Operating contract
- Workflow
- 1. Pass the repository-understanding gate
- 2. Validate the journey contract
- 3. Preflight without changing product behavior
- 4. Interpret and execute the Markdown
- 5. Judge once, retry carefully
- 6. Clean up and hand off
- Demonstration examples
- Failure handling
What does the run-smoke-tests skill do?
Inspect an unfamiliar repository, interpret a broad Markdown user journey at runtime, operate the real product through its supported web, API, CLI, desktop, or mobile surface, and produce an auditable pass, fail, or blocked judgment with screenshots, logs, recordings, and a step timeline when available. Use when asked to run smoke tests, validate an end-to-end user journey, dogfood a product, test a release candidate, or execute a non-deterministic workflow that may include authentication or human checkpoints. Do not use as a substitute for deterministic unit, integration, or scenario tests.
How do I install it?
Run `npx skills add tamdogood/builder-essential-skills --skill run-smoke-tests --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From tamdogood/builder-essential-skills, a repository with 90 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.