/mcp-check
Use to check MCP server prerequisites before activating or using a server.
$ 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-check
Context preview
What this command does when you run it.
Use to check MCP server prerequisites before activating or using a server.
Command definition
mcp-check.mdmcp-check
Use to check MCP server prerequisites before activating or using a server.
Steps:
1. Identify the MCP server name. 2. Run: `apx mcp check <name>`
- Verifies required commands exist (docker, npx, etc.).
- Verifies required env vars are set.
- Parses the config file for syntax errors.
3. Report: which prerequisites pass, which fail, and the exact blocker.
Do not start or install the MCP server unless all prerequisites pass and the user approves.
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-smoke
Use to verify an MCP server starts and responds before adding it to an agent config.
Open command