Execute fast smoke tests validating critical functionality after deployment.

MITAuto-check passedTesting & QA

Install Running Smoke Tests

skills CLI
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill running-smoke-tests -a claude-code

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

GitHub CLI
$ gh skill install jeremylongshore/tons-of-skills-marketplace running-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/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/.curated/running-smoke-tests .claude/skills/running-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
running-smoke-tests
GitHub stars
2.8k
Token cost
~1.4k tokens
SKILL.md length
482 words
Files
4 (incl. scripts, references, assets)
Skills in repo
3,342
Repo updated
First seen
Licence
MIT

At a glance

Execute fast smoke tests validating critical functionality after deployment.

  • Works in 7 steps: Identify the critical paths that… → Create a smoke test configuration… → Write the smoke test suite as a… → …
  • Performing specialized testing
  • SKILL.md covers Overview, Prerequisites, Instructions and Output, plus 3 more sections
  • Calls curl

What it does

Running Smoke Tests is an agent skill from jeremylongshore/tons-of-skills-marketplace. Execute fast smoke tests validating critical functionality after deployment. Use when performing specialized testing. Trigger with phrases like "run smoke tests", "quick validation", or "test critical paths".

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including scripts, reference files and assets (for example `assets/README.md`, `references/README.md` and `scripts/README.md`). Compatibility notes: Designed for Claude Code

It sits in Testing & QA, covering QA and bug reports. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.

When your agent uses it

  • Performing specialized testing
  • With phrases like run smoke tests
  • Quick validation
  • Test critical paths

Example prompts

  • “run smoke tests”
  • “quick validation”
  • “test critical paths”
  • “/running-smoke-tests”

Requirements

  • Compatibility (from SKILL.md): Designed for Claude Code
  • Pre-approved tools (allowed-tools): Read, Write, Edit, Grep, Glob, Bash(test:smoke-*)

Workflow steps

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

  1. Identify the critical paths that constitute a "working" application
  2. Create a smoke test configuration listing each check
  3. Write the smoke test suite as a lightweight script or test file
  4. Implement timeout guards
  5. Add deployment-gate integration
  6. Store smoke test results as CI artifacts for audit trail.
  7. Schedule periodic smoke runs (every 5 minutes in production) as synthetic monitoring.

What it can do on your machine

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

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Write
    • Edit
    • Grep
    • Glob
    • Bash(test:smoke-*)

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 1 file in scripts/, which the agent can run.

    Shell commands in SKILL.md call:

    • curl

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

  • Network

    Links to these hosts (documentation or services it may open):

    • martinfowler.com
    • playwright.dev
    • curl.se
    • docs.github.com

    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.

  • Compatibility

    Designed for Claude Code

    From compatibility in the SKILL.md frontmatter.

Context cost

Running Smoke Tests loads about 1.4k tokens when it runs, and up to ~1.4k if it reads all its reference files. Until then it costs about 57 tokens; SKILL.md has 482 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~57
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.4k

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); the scripts in this folder are not scanned.

SKILL.md

The full file from jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 482 words, ~1,383 tokens.

Download SKILL.mdSave it as .claude/skills/running-smoke-tests/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
running-smoke-tests
description
Execute fast smoke tests validating critical functionality after deployment. Use when performing specialized testing. Trigger with phrases like "run smoke tests", "quick validation", or "test critical paths".
allowed-tools
Read, Write, Edit, Grep, Glob, Bash(test:smoke-*)
compatibility
Designed for Claude Code
version
1.20.0
author
Jeremy Longshore <jeremy@intentsolutions.io>
license
MIT
tags
testing, deployment, smoke-tests

Smoke Test Runner

Overview

Execute fast, high-confidence smoke tests that validate critical application functionality after deployment or build. Smoke tests verify that the application starts, core user flows work, and key integrations respond -- without running the full test suite.

Prerequisites

  • Application deployed and accessible at a known URL or running locally
  • HTTP client available (curl, wget, node-fetch, or Playwright)
  • List of critical endpoints and user flows to validate
  • Expected response codes and content patterns for each check
  • CI/CD pipeline hook for post-deployment validation

Instructions

  1. Identify the critical paths that constitute a "working" application:
    • Health check endpoint returns 200 with expected body.
    • Homepage loads and contains key UI elements.
    • Authentication flow succeeds with test credentials.
    • Primary API endpoint returns valid data.
    • Database connection is active and responding.
  2. Create a smoke test configuration listing each check:
    • URL or command to execute.
    • Expected HTTP status code (200, 301, etc.).
    • Response body pattern to match (substring or regex).
    • Maximum acceptable response time (e.g., 3 seconds).
  3. Write the smoke test suite as a lightweight script or test file:
    • Use curl for HTTP checks or Playwright for browser-based checks.
    • Run checks sequentially for simplicity (parallel for speed if independent).
    • Fail fast on the first critical failure.
    • Log each check result with pass/fail, response time, and status code.
  4. Implement timeout guards:
    • Set a global timeout of 60 seconds for the entire smoke suite.
    • Set per-check timeouts of 5-10 seconds.
    • Treat timeouts as failures, not retries.
  5. Add deployment-gate integration:
    • On success: proceed with deployment promotion or traffic shifting.
    • On failure: trigger rollback and send alert notification.
    • Report results to CI/CD dashboard and Slack/Teams webhook.
  6. Store smoke test results as CI artifacts for audit trail.
  7. Schedule periodic smoke runs (every 5 minutes in production) as synthetic monitoring.
Show full SKILL.md (187 more words)Show less

Output

  • Smoke test script (scripts/smoke-test.sh or tests/smoke.test.ts)
  • Pass/fail result for each critical check with response times
  • Deployment gate verdict (PASS or FAIL with reason)
  • CI artifact with timestamped smoke test log
  • Alert payload for failed checks (Slack webhook, PagerDuty, etc.)

Error Handling

ErrorCauseSolution
Connection refusedApplication not yet ready after deploymentAdd a startup wait with exponential backoff (max 30 seconds) before running smoke tests
503 Service UnavailableApplication is starting or behind a load balancer drainingRetry with 2-second delay up to 3 times; check load balancer health check status
Unexpected redirect (301/302)URL changed or SSL redirect not accounted forFollow redirects with curl -L; update expected URLs in smoke config
Content mismatchPage content changed but smoke test pattern is too specificUse broad patterns (check for <title> or key element IDs, not exact text)
Timeout on database checkDatabase migration running or connection pool exhaustedIncrease timeout for database checks; verify migration completed before smoke tests

Examples

Shell-based smoke test script:

bash
#!/bin/bash
set -e
BASE_URL="${1:-http://localhost:3000}"  # 3000: 3 seconds in ms
PASS=0; FAIL=0

check() {
  local name="$1" url="$2" expected="$3"
  status=$(curl -s -o /dev/null -w '%{http_code}' --max-time 5 "$url")
  if [ "$status" = "$expected" ]; then
    echo "PASS: $name (HTTP $status)"
    ((PASS++))
  else
    echo "FAIL: $name (expected $expected, got $status)"
    ((FAIL++))
  fi
}

check "Health check" "$BASE_URL/health" "200"  # HTTP 200 OK
check "Homepage" "$BASE_URL/" "200"  # HTTP 200 OK
check "API status" "$BASE_URL/api/status" "200"  # HTTP 200 OK
check "Login page" "$BASE_URL/login" "200"  # HTTP 200 OK

echo "Results: $PASS passed, $FAIL failed"
[ "$FAIL" -eq 0 ] || exit 1

Playwright smoke test:

typescript
import { test, expect } from '@playwright/test';

test('homepage loads with navigation', async ({ page }) => {
  await page.goto('/', { timeout: 10000 });  # 10000: 10 seconds in ms
  await expect(page.locator('nav')).toBeVisible();
  await expect(page).toHaveTitle(/My App/);
});

test('API health endpoint responds', async ({ request }) => {
  const response = await request.get('/api/health');
  expect(response.ok()).toBeTruthy();
  expect(await response.json()).toHaveProperty('status', 'ok');
});

Resources

© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files (scripts, references, assets) in skills/.curated/running-smoke-tests of jeremylongshore/tons-of-skills-marketplace.

  • SKILL.md
  • assets/README.md
  • references/README.md
  • scripts/README.md

Open the folder on GitHubat commit cfae287

Compare with similar skills

Running 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.

Running Smoke Tests compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Running Smoke Tests this skilljeremylongshore/tons-of-skills-marketplace2.8k—~1.4kAutomated safety check: PassMIT
Reproduce Chat Statesdifferent-ai/openwork24k—~673Automated safety check: PassCustom licence
Dynamo Jira TicketDynamoDS/Dynamo2k—~1.1kAutomated safety check: PassApache-2.0
Moav E2EMotherofallVPNs/MoaV449—~1.9kAutomated safety check: NotesMIT
Creating A Coral TaskHuman-Agent-Society/CORAL1.1k—~2.2kAutomated safety check: PassApache-2.0
Launch Rlmarin-community/marin3.9k—~894Automated safety check: PassApache-2.0

Similar skills

  • Reproduce Chat States

    different-ai/openwork

    Fires known chat states in the running OpenWork desktop app, such as provider errors, retries and tool steps, so you can check how each renders.

    24k GitHub stars~673 tokensUpdated today
    Testing & QAAuto-check passed
  • Dynamo Jira Ticket

    DynamoDS/Dynamo

    Create structured Jira tickets for Dynamo from bug reports, failing tests, or feature requests.

    2k GitHub stars~1.1k tokensUpdated yesterday
    Testing & QAAuto-check passed
  • Moav E2E

    MotherofallVPNs/MoaV

    Run and debug MoaV's end-to-end tests — real protocol connectivity (client-test.sh) and the moav CLI smoke test — against a LIVE server, via the self-hosted e2e workflow or a local test VPS.

    449 GitHub stars~1.9k tokensUpdated 4 days ago
    Testing & QAAuto-check: notes
  • Creating A Coral Task

    Human-Agent-Society/CORAL

    Author a new CORAL task — the three pieces that must line up (task.yaml, seed/, a packaged grader/), the coral init → coral validate → smoke-test loop, and how to pick a grader pattern (stdout…

    1.1k GitHub stars~2.2k tokensUpdated 1 mo ago
    Testing & QAAuto-check passed
  • Launch Rl

    marin-community/marin

    Define, validate, submit, or restart a Marin SkyRL experiment through its artifact main.

    3.9k GitHub stars~894 tokensUpdated today
    Testing & QAAuto-check passed
  • Actionbook Web Test

    actionbook/actionbook

    Run browser-based web tests against websites using Actionbook CLI.

    1.6k GitHub stars~9.7k tokensUpdated 1 mo ago
    Testing & QAAuto-check passed

More from jeremylongshore/tons-of-skills-marketplace

All 3,342 skills in this repo
  • Performing Security Code Review

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.

    2.8k GitHub starsUsed in 2 repos~1.3k tokens
    Auto-check: notes
  • Adapting Transfer Learning Models

    jeremylongshore/tons-of-skills-marketplace

    Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Agent Context Loader

    jeremylongshore/tons-of-skills-marketplace

    Execute proactive auto-loading: automatically detects and loads agents.md files.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Aggregating Performance Metrics

    jeremylongshore/tons-of-skills-marketplace

    Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.

    2.8k GitHub stars~1.2k tokensUpdated today
    Auto-check passed
  • Analyzing Capacity Planning

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.

    2.8k GitHub stars~947 tokensUpdated today
    Auto-check passed
  • Analyzing Database Indexes

    jeremylongshore/tons-of-skills-marketplace

    Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.

    2.8k GitHub stars~2k tokensUpdated today
    Auto-check passed

Categories

Questions about Running Smoke Tests

What does Running Smoke Tests do?

Execute fast smoke tests validating critical functionality after deployment. Running Smoke Tests is an agent skill from jeremylongshore/tons-of-skills-marketplace. Execute fast smoke tests validating critical functionality after deployment.

When should I use Running Smoke Tests?

Running Smoke Tests fits situations like: performing specialized testing; with phrases like run smoke tests; quick validation; test critical paths.

How do I install Running Smoke Tests in Claude Code?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill running-smoke-tests -a claude-code`. Or copy the skill folder (skills/.curated/running-smoke-tests in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/running-smoke-tests in your project. Claude Code loads it when a task matches its description.

How do I install Running Smoke Tests in Codex?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill running-smoke-tests -a codex`. Or copy the skill folder (skills/.curated/running-smoke-tests in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/running-smoke-tests in your project. Codex loads it when a task matches its description.

Can I use Running 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 jeremylongshore/tons-of-skills-marketplace --skill running-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/running-smoke-tests, .gemini/skills/running-smoke-tests, .github/skills/running-smoke-tests and .opencode/skills/running-smoke-tests in your project.

What does Running Smoke Tests need to run?

Going by SKILL.md and its folder, Running Smoke Tests needs the command-line tools its instructions call (curl). Its frontmatter pre-approves these tools: Read, Write, Edit, Grep, Glob, Bash(test:smoke-*). Compatibility (from SKILL.md): Designed for Claude Code.

Does Running Smoke Tests access the network?

SKILL.md names 4 domains. As links in the text: martinfowler.com, playwright.dev, curl.se and docs.github.com. This is read from the text; nothing was executed.

Is Running 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Running Smoke Tests use?

Running Smoke Tests is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Running Smoke Tests use?

About 1.4k tokens (SKILL.md is roughly 5.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 15 tokens, read only when the agent opens those files.

What are the alternatives to Running Smoke Tests?

Skills that share tags, products or a category with Running Smoke Tests: Reproduce Chat States (different-ai/openwork, 24k stars), Dynamo Jira Ticket (DynamoDS/Dynamo, 2k stars), Moav E2E (MotherofallVPNs/MoaV, 449 stars) and Creating A Coral Task (Human-Agent-Society/CORAL, 1.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Running Smoke Tests?

jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,827 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 10, 2026.

Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.