/mcp-smoke
Use to verify an MCP server starts and responds before adding it to an agent config.
$ npx -y skills add yeaight7/agent-powerups --agent claude-codeHow it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/mcp-smoke
Context preview
What this command does when you run it.
Use to verify an MCP server starts and responds before adding it to an agent config.
Command definition
mcp-smoke.mdmcp-smoke
Use to verify an MCP server starts and responds before adding it to an agent config.
Steps:
1. Identify the MCP server name. 2. Run prerequisites check first: `apx mcp check <name>`. 3. If prerequisites pass, run: `apx mcp smoke <name>`. 4. Report: server started and responded OK / FAILED — with the first error line if it failed.
Do not add the server to agent config until smoke passes.
Curated power-ups for coding agents: skills, slash commands, MCP configs, hooks, AGENTS.md templates, and workflows for serious software engineering. Claude Code, Codex, Antigravity CLI, Cursor and more
Repo: yeaight7/agent-powerups
Other commands on agent-powerups.
- /bug-check
Run automated tests and build checks first, then agent code review. For each bug found, propose or document a regression test.
Open command - /build-fix
Use when a build, type check, or test suite is failing and needs to be unblocked with a minimal change.
Open command - /debug
Use when a bug needs systematic diagnosis before a fix is attempted.
Open command - /doctor
Use to diagnose environment, tooling, and Agent Powerups setup problems.
Open command - /implement
Use to turn a spec or user request into working, tested code.
Open command - /mcp-check
Use to check MCP server prerequisites before activating or using a server.
Open command