running-web-smoke-test

Runs a fast single-page pass/fail check for page load, console errors, broken images, and expected content.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/celikgo/webmobai --skill running-web-smoke-test-celikgo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: running-web-smoke-test
Source: https://github.com/celikgo/webmobai/tree/main/.claude/skills/running-web-smoke-test
Command: npx skills add https://github.com/celikgo/webmobai --skill running-web-smoke-test-celikgo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After a deploy or when a user reports "something is wrong", you need a quick answer to one question: does the site basically work? Full audits are slow and overkill for this. This Skill runs a narrow, sub-minute browser check that catches obvious regressions — page errors, console blow-ups, broken images, missing critical content — without crawling or deep performance measurement. ## Core Features & Use Cases - Structured pass/fail workflow: Launch a browser, navigate, snapshot page state, check console errors and broken images, assert expected content, take one screenshot, and close — all via WebMobAI MCP tools. - Clear failure triage: Distinguishes site failures from environment problems (missing chromium, unreachable target) using webmobai-doctor, and treats login-walled pages as "blocked, not failed" rather than false passes. - Authenticated smoke tests: Supports relaunching with a storage_state_path session file so post-deploy checks work behind a login. - Use Case: You just deployed to staging and want to verify the homepage loads, shows no console errors, and still renders the "Sign Up" button — with a screenshot as evidence — in under 60 seconds. ## Quick Start Run a smoke test on https://staging.example.com and confirm the "Sign Up" button is present.

Frequently Asked Questions about running-web-smoke-test

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a quick smoke test on a website after deployment?▼

Launch a browser with WebMobAI, navigate to the URL, snapshot the page state, check for console errors and broken images, verify any expected content, and take one screenshot. The whole pass takes under 60 seconds and reports a structured PASS or FAIL.

What is the difference between a smoke test and a full web app audit?▼

A smoke test is a narrow, fast single-page check answering whether the site basically works — page loads, no console errors, no broken images, key elements present. A full audit adds Web Vitals, accessibility checks, multi-breakpoint testing, and report generation, which are deliberately out of scope here.

Can I smoke test a page that sits behind a login?▼

Yes, by relaunching the browser with a storage_state_path pointing to a saved session file such as auth.json, so the test starts already authenticated. If the final URL lands on the login page, the session has expired and must be re-captured.

Why does my smoke test fail before the page even loads?▼

Launch errors, a missing chromium binary, or an unreachable target are environment problems, not site regressions. Run webmobai-doctor to check Node version, browser installs, and API key configuration before re-running the test.

Should console warnings fail a website smoke test?▼

No. Only console errors and broken images count as smoke-test failures, because many production sites emit benign warnings. Warnings are reported in the output but do not affect the PASS/FAIL verdict.