smoke-test

Smoke Test is a Claude Code skill from the Mastra project that scaffolds a fresh Mastra application with create-mastra and then smoke-tests the resulting Mastra Studio in Chrome via the Chrome MCP server. It solves the problem of quickly validating that a given create-mastra release, package manager, and LLM provider combination produces a working project and a functioning Studio UI, which is useful for release verification and regression checking.

The skill is parameter-driven: required flags for target directory, project name, and version tag, plus optional flags for package manager (npm, yarn, pnpm, or bun) and LLM provider (openai, anthropic, groq, google, cerebras, or mistral). It begins with strict parameter parsing and validation, then runs create-mastra non-interactively with all components and example code, verifies the generated project structure, optionally adds a browser-enabled agent for browser testing, configures the single required provider API key (checking the global environment first, then the project .env, and asking the user only if needed), starts the dev server (typically on localhost:4111), and drives the Studio through Chrome MCP tools like navigate, click, type, and screenshot to run a smoke-test checklist.

It targets Mastra maintainers, contributors, and QA engineers who need a repeatable end-to-end sanity check of the framework's project generator and Studio. It requires the Chrome MCP server (Claude-in-Chrome) to be configured. API-key handling follows standard, security-conscious practice: it only checks for the one key matching the chosen provider and prefers existing environment values before prompting.