Menu
Archived n8n workflow operations guidance kept for historical reference; do not use for new active routing.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Blog writing operations: concrete drafts, diagnosis, comment strategy, external sources, and recurring gotchas.
사용자 요청을 Blog, Luna, Darwin, Sigma, Ska, Hub/Orchestrator 등 적절한 팀과 런타임으로 라우팅할 때 사용.
Use for non-trivial production code changes that require expert challenge and consensus, test-first implementation, soft and read-only hard verification, runtime and DB consistency checks, refactoring discipline, and an independent code-review gate.
Use when diagnosing or improving Luna investment-team autonomous operation bottlenecks, especially the 30-minute Codex automation loop, live-fire watchdog issues, LLM hot-path overuse, discovery funnel stalls, marketdata connectivity, reconcile blockers, or safe fix planning.
Hub routing, resilience, alarm lifecycle, and Sigma feedback operations.
Darwin research cycle operations: cycle overview, predicate authoring, adopt review, and recurring gotchas.
| name | n8n-workflow-ops |
| description | Archived n8n workflow operations guidance kept for historical reference; do not use for new active routing. |
| triggers | ["archived n8n workflow ops"] |
| permissions | ["read-only"] |
| owner | platform |
This skill was moved out of the active skills/ root by the O3 interface standard cleanup.
Use current Hub/Orchestrator runbooks for new workflow operations. This archived copy is retained only to preserve historical guidance.
이 스킬은 이 저장소에서 n8n workflow, setup script, live webhook, healthz, registry path, workflow 재생성 작업을 할 때 사용한다.
packages/core/lib/n8n-setup-client.jspackages/core/lib/n8n-webhook-registry.jspackages/core/lib/health-provider.js팀별 setup/diagnostic:
bots/orchestrator/n8n/setup-n8n.js, bots/orchestrator/n8n/setup-ska-workflows.js, bots/orchestrator/scripts/check-n8n-critical-path.jsbots/blog/n8n/setup-blog-workflows.js, bots/blog/scripts/check-n8n-pipeline-path.jsbots/reservation/n8n/setup-ska-command-workflow.ts, bots/reservation/scripts/check-n8n-command-path.ts기존 것이 있으면 스킵하지 말고 안전하게 교체한다.healthz ok와 webhook registered는 별개로 본다.n8n-setup-client.js를 사용 중인지 확인한다.아래 순서로 본다.
healthz 응답webhook_entity 기반 production path 해석404 not registered면 정적 /webhook/foo만 보지 말고 registry resolved URL을 먼저 확인한다.
{{ ... }}나 \n 원문이 그대로 보이면 workflow 템플릿 표현식을 먼저 본다.node --check <setup-or-check-script>node bots/orchestrator/scripts/check-n8n-critical-path.jsnode bots/blog/scripts/check-n8n-pipeline-path.jsnode dist/ts-runtime/bots/reservation/scripts/check-n8n-command-path.jsNaN/undefined가 외부로 노출되지 않는가