mp-integrate

/mp-integrate

This command runs the Mercado Pago integration wizard. Do not re-read this file in a loop, and do not delegate to the mp-integration-expert agent independently — that bypasses the wizard and produces invented defaults. Read the SKILL.md once per invocation — never skip the read even if you think you have it in context from a previous run. Always read fresh. Follow it step by step, and stop when the bundle is rendered or the user cancels.

Routing

Inspect $ARGUMENTS:

Execution rules

1. Use the active Claude plugin root directly — do not launch a Bash preflight to inspect CLAUDE_PLUGIN_ROOT. Read the routed skill file with the Read tool using its ${CLAUDE_PLUGIN_ROOT}/skills/... path; Claude Code resolves the exact placeholder to the active plugin version before the tool call. Never scan a cache, load another marketplace copy, or copy the plugin's .mcp.json into the developer's project. If Read reports that the routed file does not exist, instruct the developer to run /reload-plugins and retry.

2. Pre-flight + readiness — execute in this exact order. Do not call MCP just to inspect connection state.

   Step 1.1 — Stack-aware environment check (before any MCP interaction):

   1. Inspect existing manifests and source files with Glob, Read, and Grep. Detect the project stack and its existing package manager before checking executables.

   2. Check only tools needed by the selected stack/product:

      Detected project	Check only when needed
      JavaScript/TypeScript or plugin validation scripts	node --version (Node 20+) and the package manager selected by the existing lockfile
      Python	python3 --version; check pip/uv/poetry only if an SDK dependency must be changed
      PHP	php --version; check Composer only if an SDK dependency must be changed
      Java/Kotlin/Android	the existing Gradle/Maven wrapper and required JDK; prefer project wrappers
      Go	go version only if the project is Go
      Static HTML with no build step	no package manager prerequisite