skills.rest
icednut
icednutCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

n8n-studio:analyze-workflow

Analyze n8n workflow structure and execution failures from summary JSON files.

Updated Apr 10, 2026
Search Tags:#debugging#TDD#workflow analysis#n8n#execution logs#workflow structure#summary files
One-click install
npx skills add https://github.com/icednut/n8n-studio --skill n8n-studio-analyze-workflow
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: n8n-studio:analyze-workflow
Source: https://github.com/icednut/n8n-studio/tree/main/skills/analyze-workflow
Command: npx skills add https://github.com/icednut/n8n-studio --skill n8n-studio-analyze-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill removes the guesswork when you need to understand an n8n workflow’s current structure or why an execution failed.

Core Features & Use Cases

  • Workflow structure analysis from summary files: Reads workflow/*/summary/*.json to extract workflow_id, workflow_name, and node-level summaries.
  • Execution log analysis by Execution ID: Retrieves logs for failure point identification and builds likely root-cause hypotheses.
  • Discovery of similar workflows: When developing new functionality, scans existing summaries and suggests up to 3 relevant reference workflows.

Quick Start

Ask n8n-studio to analyze a specific workflow (by ID or name) and, if you have one, include the Execution ID to inspect failure logs for remediation.

Frequently Asked Questions about n8n-studio:analyze-workflow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I analyze an n8n workflow structure from summary JSON files?▼

You can analyze an n8n workflow structure by parsing `workflow/*/summary/*.json` files to extract workflow IDs, names, and node-level summaries into a structured output.

How do I debug failed n8n workflow executions using an Execution ID?▼

Debug failed n8n workflow executions by providing an Execution ID to retrieve execution logs, identify the failure point, and generate likely root-cause hypotheses.

Can I find similar existing n8n workflows to reference for new development?▼

Yes, you can find similar existing n8n workflows by scanning existing summary JSON files, which suggests up to 3 relevant reference workflows to accelerate new development.

What do I need to diagnose an n8n workflow execution failure?▼

To diagnose an n8n workflow execution failure, you need the workflow ID or name to locate summary JSON files, and optionally an Execution ID to fetch logs for root-cause analysis.

Why does my n8n workflow execution fail at a specific node?▼

Your n8n workflow execution fails at a specific node due to configuration or connection issues, which execution logs retrieved via Execution ID help identify and analyze.

Related Skills

Explore More Software Engineering Skills→
icednuticednut

n8n-studio:analyze-workflow-input

Analyze n8n workflow trigger input data from a past execution.

Community
Intermediate
EmeaAppGbbEmeaAppGbb

prd-generator

Generate Product Requirements Documents from existing codebases via static analysis.

Official
Advanced
n8n-ion8n-io
421

n8n-debugging

Diagnose failing n8n workflow executions using execution data and node schemas.

Official
Advanced
NachoOsellaNachoOsella
6

explore

Find files, search keywords, and map codebase structure across large repositories.

Community
Intermediate