一键在 Manus 中运行任何 Skill

n8n-status

星标1

分支2

更新时间2026年5月18日 20:29

Show the health and status of the local n8n automation stack. Use when the user asks about n8n status, health, whether it is running, or which containers are up.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

strapi

strapi/community

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

n8n-status

Prints container status plus health probes for n8n and (if running) n8n-mcp.

Steps

List containers:
```
pnpm --filter automation n8n:ps
```

Probe n8n health:

curl -sf -o /dev/null -w '%{http_code}\n' http://localhost:5678/healthz || echo 'unreachable'

A 200 means healthy. Anything else means n8n isn't ready (or isn't running).

Probe n8n-mcp health (only if its container is running):

curl -sf -o /dev/null -w '%{http_code}\n' http://localhost:3100/health || echo 'unreachable'

Summarize per service in one line each:
- engine (docker compose vs podman-compose, from apps/automation/scripts/compose.sh)
- container state (running / exited / healthy)
- local URL and probe result

Notes

If both probes fail but containers show as running, it usually means the service is still booting. Wait ~20s and retry, or inspect logs: pnpm --filter automation n8n:logs.

同仓库更多 Skills

同仓库

n8n-start

strapi/community

Start the local n8n instance for the Strapi community hub. Use when the user asks to start, launch, bring up, or run n8n or the automation stack. Pass --mcp to also bring up n8n-mcp (requires N8N_API_KEY and MCP_AUTH_TOKEN in .env).

2026-05-181

n8n-export

strapi/community

Export all workflows from the local n8n instance into version-controlled JSON under apps/automation/workflows/. Use when the user asks to export, pull, snapshot, or sync workflows from the local n8n.

2026-05-181

n8n-import

strapi/community

Import workflows from apps/automation/workflows/ into the local n8n instance. Use when the user asks to import, push, load, or sync workflow JSON files to the local n8n.

2026-05-181

n8n-restart

strapi/community

Restart the local n8n automation stack, preserving whatever profile (plain or mcp) is currently running. Use when the user asks to restart, reload, or reboot n8n.

2026-05-181

n8n-stop

strapi/community

Stop the local n8n automation stack. Use when the user asks to stop, shut down, halt, or bring down n8n. Data in the n8n_data volume persists across stops.

2026-05-181

n8n-workflow-builder

strapi/community

Domain-expertise guide for designing, building, validating, and modifying n8n workflows using the n8n-mcp tools. Use whenever the user asks to build, create, design, edit, or validate an n8n workflow. Requires the n8n-mcp server to be running (see n8n-start).

2026-05-181

name	n8n-status
description	Show the health and status of the local n8n automation stack. Use when the user asks about n8n status, health, whether it is running, or which containers are up.

n8n-status

Prints container status plus health probes for n8n and (if running) n8n-mcp.

Steps

List containers:
```
pnpm --filter automation n8n:ps
```

Probe n8n health:

curl -sf -o /dev/null -w '%{http_code}\n' http://localhost:5678/healthz || echo 'unreachable'

A 200 means healthy. Anything else means n8n isn't ready (or isn't running).

Probe n8n-mcp health (only if its container is running):

curl -sf -o /dev/null -w '%{http_code}\n' http://localhost:3100/health || echo 'unreachable'

Summarize per service in one line each:
- engine (docker compose vs podman-compose, from apps/automation/scripts/compose.sh)
- container state (running / exited / healthy)
- local URL and probe result

Notes

If both probes fail but containers show as running, it usually means the service is still booting. Wait ~20s and retry, or inspect logs: pnpm --filter automation n8n:logs.