deploy-smoke-test

Name: deploy-smoke-test
Availability: InStock
Author: paulmalmquist

Automate post-deploy smoke tests for Vercel deployments and admin login.

Updated Jan 22, 2026

Search Tags:#monitoring #vercel #pipeline #deploy #browser-automation #smoke-test #admin-login

Ready to run

npx skills add https://github.com/paulmalmquist/Consulting_app --skill deploy-smoke-test

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: deploy-smoke-test
Source: https://github.com/paulmalmquist/Consulting_app/tree/main/skills/deploy-smoke-test
Command: npx skills add https://github.com/paulmalmquist/Consulting_app --skill deploy-smoke-test

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the tedious post-deploy verification process, ensuring production health by validating Vercel deployments, admin access, and core modules before demos or afternoon meetings.

Core Features & Use Cases

Post-deploy verification across Vercel deployment status, admin login, and critical modules (Fund Portfolio, AI Chat Bug 0, Deal Radar, and novendor.ai).
Browser-based smoke tests that render key pages, verify branding, and confirm UI elements and flows function as expected.
Time-bound checks run at 10:30 AM after the morning deploy window to catch regressions before important meetings.

Quick Start

Run the deploy-smoke-test after every production deployment to automatically validate Vercel deployments, admin login, and core module health.

Frequently Asked Questions about deploy-smoke-test

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

FAQPage Schema

How do I automate post-deploy smoke tests for Vercel deployments?▼

Post-deploy smoke tests for Vercel deployments are automated by verifying deployment status, performing browser-based admin logins, and validating critical UI modules to ensure production health before meetings.

What is a post-deploy smoke test and when should I run it?▼

A post-deploy smoke test verifies production health by rendering key pages and checking UI flows. It should be run after the morning deploy window around 10:30 AM to catch regressions before afternoon meetings.

Can I use browser automation to verify admin login and UI elements after a production deploy?▼

Yes, browser automation is used to perform admin logins, render key pages, verify branding, and confirm UI elements and flows function as expected during post-deploy production health checks.

Do I need Vercel MCP tooling to run browser-based production health checks?▼

Yes, Vercel MCP tooling is required alongside browser automation capabilities to execute the production health checks and load the UI smoke-test steps into context upon activation.

What's the best way to catch deployment regressions before a demo?▼

The best way to catch deployment regressions before a demo is to run time-bound post-deploy verification checks that validate Vercel status, admin access, and critical modules like AI Chat and Deal Radar.