Individual skill
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.
skills/run-smoke-tests/SKILL.md
Source commit 1be9984bdafbb68eaff400bdd82773a1d41ee7ec
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 6, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 227
- Repository last updated
- Aug 16, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent Repository topic
- ai Repository topic
- ai-agents Repository topic
- claude-code Repository topic
- claude-code-plugin Repository topic
- claude-skills Repository topic
- codex Repository topic
- codex-skill Repository topic
- hermes-agent Repository topic
- openclaw Repository topic
- operations Derived category
- security Derived category
- testing Derived category
- testing-browser Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
README.mddoc · 679 bytesSKILL.mdcore · 7,625 bytesSKILL.mdcore · 7,625 bytesSKILL.mdcore · 7,625 bytesSKILL.mdcore · 7,625 bytesagents/openai.yamlasset · 246 bytesexamples/developer-cli-first-run.smoke.mddoc · 3,420 bytesexamples/saas-team-onboarding.sample-report.mddoc · 2,263 bytesexamples/saas-team-onboarding.smoke.mddoc · 3,585 bytesreferences/smoke-format.mddoc · 2,244 bytes
Read excerpt
# 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