From n8n-autopilot
Verifies n8n-autopilot setup — n8nac CLI presence, workspace binding, n8n API reachability, and companion plugin `n8n-as-code` status. Use after setup, upgrades, or when commands behave unexpectedly.
How this skill is triggered — by the user, by Claude, or both
Slash command
/n8n-autopilot:check-mcpsThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
n8n-autopilot is CLI-only (`npx n8nac …`). There is no MCP server entry for this plugin — the `mcp__n8n-as-code__*` namespace seen in older docs was an upstream assumption that never landed (the npm `n8nac mcp` entry-point is broken and Etienne's companion plugin ships skill knowledge, not an MCP server).
n8n-autopilot is CLI-only (npx n8nac …). There is no MCP server entry for this plugin — the mcp__n8n-as-code__* namespace seen in older docs was an upstream assumption that never landed (the npm n8nac mcp entry-point is broken and Etienne's companion plugin ships skill knowledge, not an MCP server).
This skill verifies the actually-required layers.
npx n8nac --version 2>&1
Expect 2.2.0 or higher. Anything below is unsupported.
bash "$CLAUDE_PLUGIN_ROOT/scripts/setup-check.sh" 2>&1
($CLAUDE_PLUGIN_ROOT is set by Claude Code when running plugin commands — no manual path needed.)
Inspect the output. The script checks, in order:
npx availableworkspace status --json returns env config)n8n-as-code@n8nac-marketplace enabled (warns if missing — the companion's n8n-architect skill is the primary source of n8n authoring knowledge)n8n-as-code) enabledgrep -q '"n8n-as-code@n8nac-marketplace": true' "$HOME/.claude/settings.json" && \
echo "OK: n8n-as-code companion enabled" || \
echo "WARN: n8n-as-code companion not enabled — install it for best UX:
claude plugin marketplace add EtienneLescot/n8n-as-code
claude plugin install n8n-as-code@n8nac-marketplace"
node "$CLAUDE_PLUGIN_ROOT/skills/find-project/scripts/list.js"
Prints the workspace-pinned project plus every project derivable from credential ownership. Surface the table to the user — multi-project blindness (referencing creds from the wrong project) is the most common cause of "workflow pushes but fails at runtime".
Print a one-line summary per layer, plus the most likely fix for any FAIL:
Layer | Status
───────────────────────────────────┼─────────
n8nac CLI (>= 2.2.0) | OK
workspace bound | OK
n8n API reachable | OK
companion plugin (n8n-as-code) | OK
schemas/_index.json present | OK
For any non-OK row, surface the line from setup-check.sh verbatim — that script already prints the suggested fix.
npx claudepluginhub neurawork-git/n8n-autopilot --plugin n8n-autopilotCurated mapping of user intents to exact n8nac CLI commands for 60+ workflows. Use this before the reference or --help.
Runs comprehensive diagnostics on Claude Code environment: plugins, settings, hooks, MCP servers. Identifies issues, supports --fix and --verbose.
This skill should be used when the user asks to "check my setup", "run diagnostics", "doctor", "health check", "verify my installation", "are my plugins working", "check plugin status", "what's broken", "fix my setup", "debug my environment", "check dependencies", "environment check", "troubleshoot setup", or invokes /midnight-expert:doctor. Provides comprehensive health reporting for the midnight-expert ecosystem — plugin installation, MCP servers, external tools, cross-plugin references, and NPM registry.