How do I install the Webapp Deploy Smoke Test skill?

Run npx skillmds@latest add tomevault-io/webapp-deploy-smoke-test in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Webapp Deploy Smoke Test safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Webapp Deploy Smoke Test?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Webapp Deploy Smoke Test free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Webapp Deploy Smoke Test?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Webapp Deploy Smoke Test by tomevault-io

Name: Webapp Deploy Smoke Test
Author: tomevault-io

Webapp Deploy Smoke Test

Run the Open StarTer Village external-network deploy smoke test after Fly.io alpha deployments or when verifying a fork. Use when checking public frontend availability, public game server health, multiplayer WebSocket behavior, reconnect behavior, latency, restart limitations, or UptimeRobot Discord alerting. Use when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

Webapp External-Network Deploy Smoke Test

Overview

Use this workflow after deploying the Fly.io alpha from a real external network. Do not rely only on localhost, a Fly private network, or logs from inside the deployment environment.

Inputs

Confirm these values before running the test:

Public app origin, for example https://open-star-ter-village.fly.dev
Public game server origin, usually the app origin on port 3001
GitHub issue or PR where the run should be recorded
Whether the user authorizes alert tests or production restarts

Public Probes

Run these checks from outside Fly.io:

GET https://<app>/ returns HTTP 200.
GET https://<app>/lobby returns HTTP 200.
GET https://<app>:3001/health returns HTTP 200 JSON.
GET https://<app>:3001/games/OpenStarTerVillage returns HTTP 200 JSON.

If a check fails, collect the status code, response body, timestamp, and the network used before moving on.

Multiplayer Smoke Test

Use browsers or devices from real external networks when available. If three distinct networks are not available, record the limitation instead of implying full coverage.

Phone on cellular opens https://<app>/lobby and the page loads.
Three browsers from different networks create and join a 3-player match.
Socket.IO handshake succeeds; DevTools Network shows WebSocket frames flowing.
One client refreshes and reconnects within 5 seconds.
Move latency is under 300 ms RTT.
Server restart loses match state, and testers see or receive the documented alpha limitation.

Do not restart production or deliberately break a live match unless the user explicitly authorizes that action.

UptimeRobot Alert Test

Confirm the three UptimeRobot monitors cover:

Frontend: https://<app>/
Game server health: https://<app>:3001/health
Game server lobby REST: https://<app>:3001/games/OpenStarTerVillage

When the user asks to test notifications, use UptimeRobot's test notification flow and verify the Discord ops channel receives the alert. Do not expose webhook URLs, API keys, or other secrets in reports.

Report Format

Record the result as a GitHub issue or PR comment. Include:

Run date and timezone
App URL and game server URL
Tester networks and browser/device mix
Pass/fail status for each public probe and gameplay check
Failures, screenshots, logs, and response snippets
Whether UptimeRobot Discord notification was verified
Any untested item and the reason it was skipped

Source: ocftw/open-star-ter-village — distributed by TomeVault.

---name: webapp-deploy-smoke-testdescription: Run the Open StarTer Village external-network deploy smoke test after Fly.io alpha deployments or when verifying a fork. Use when checking public frontend availability, public game server health, multiplayer WebSocket behavior, reconnect behavior, latency, restart limitations, or UptimeRobot Discord alerting. Use when this capability is needed.---# Webapp External-Network Deploy Smoke Test## OverviewUse this workflow after deploying the Fly.io alpha from a real external network.Do not rely only on localhost, a Fly private network, or logs from inside thedeployment environment.## InputsConfirm these values before running the test:- Public app origin, for example `https://open-star-ter-village.fly.dev`- Public game server origin, usually the app origin on port `3001`- GitHub issue or PR where the run should be recorded- Whether the user authorizes alert tests or production restarts## Public ProbesRun these checks from outside Fly.io:- `GET https://<app>/` returns HTTP 200.- `GET https://<app>/lobby` returns HTTP 200.- `GET https://<app>:3001/health` returns HTTP 200 JSON.- `GET https://<app>:3001/games/OpenStarTerVillage` returns HTTP 200 JSON.If a check fails, collect the status code, response body, timestamp, and thenetwork used before moving on.## Multiplayer Smoke TestUse browsers or devices from real external networks when available. If threedistinct networks are not available, record the limitation instead of implyingfull coverage.- Phone on cellular opens `https://<app>/lobby` and the page loads.- Three browsers from different networks create and join a 3-player match.- Socket.IO handshake succeeds; DevTools Network shows WebSocket frames flowing.- One client refreshes and reconnects within 5 seconds.- Move latency is under 300 ms RTT.- Server restart loses match state, and testers see or receive the documented alpha limitation.Do not restart production or deliberately break a live match unless the userexplicitly authorizes that action.## UptimeRobot Alert TestConfirm the three UptimeRobot monitors cover:- Frontend: `https://<app>/`- Game server health: `https://<app>:3001/health`- Game server lobby REST: `https://<app>:3001/games/OpenStarTerVillage`When the user asks to test notifications, use UptimeRobot's test notificationflow and verify the Discord ops channel receives the alert. Do not exposewebhook URLs, API keys, or other secrets in reports.## Report FormatRecord the result as a GitHub issue or PR comment. Include:- Run date and timezone- App URL and game server URL- Tester networks and browser/device mix- Pass/fail status for each public probe and gameplay check- Failures, screenshots, logs, and response snippets- Whether UptimeRobot Discord notification was verified- Any untested item and the reason it was skipped---> Source: [ocftw/open-star-ter-village](https://github.com/ocftw/open-star-ter-village) — distributed by [TomeVault](https://tomevault.io).

Frequently asked questions