validate-workflow

Validate n8n workflow JSON files and generate Markdown reports.

1|Updated Feb 6, 2026
One-click install
npx skills add https://github.com/williamsforeal/Cyclone-SS --skill validate-workflow-williamsforeal
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: validate-workflow
Source: https://github.com/williamsforeal/Cyclone-SS/tree/main/.cursor/skills/validate-workflow
Command: npx skills add https://github.com/williamsforeal/Cyclone-SS --skill validate-workflow-williamsforeal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps prevent failed n8n imports by identifying broken structure, missing credentials, and risky placeholders before you deploy a workflow.

Core Features & Use Cases

  • Workflow health checking: Confirms required JSON fields (nodes, connections, name) and verifies the JSON structure.
  • Node-level analysis: Counts node types, detects placeholder values (TODO/FIXME), extracts required credential types, and lists webhook endpoints.
  • Credentials and connection validation: Compares credential requirements against the project .env file and checks connections for validity, orphaned nodes, and potential circular dependencies.
  • Actionable reporting: Produces a structured Markdown validation report and recommends next steps so you can safely import.

Quick Start

Ask: "/validate-workflow C:\path\to\your-workflow.json" to generate a health check report before importing into n8n.

Frequently Asked Questions about validate-workflow

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

FAQPage Schema
How do I validate an n8n workflow JSON file before importing it?

Validating n8n workflow JSON involves parsing the file to verify required fields like nodes, connections, and name. It checks node configurations, detects placeholder values, and cross-references required credentials against your .env file to prevent import failures.

Why does my n8n workflow import fail with missing credential errors?

n8n workflow imports fail when required credentials are missing or placeholders exist in the JSON. Validating the workflow cross-checks node credential types against your .env file and detects placeholders like TODO or FIXME to resolve missing credential issues.

What does n8n workflow validation check for in node connections?

n8n workflow validation checks node connections for validity, orphaned nodes, and potential circular dependencies. It inspects the JSON file connections structure to ensure all nodes are properly linked and the workflow executes safely without routing errors.

Can I extract webhook endpoints from an n8n workflow JSON before deploying?

Yes, you can extract webhook endpoints from an n8n workflow JSON before deploying. The validation process analyzes node configurations to list active webhook endpoints, helping verify external routing and connection integrity prior to import.

Does n8n workflow validation work with local .env files for credential discovery?

Yes, n8n workflow validation works with local .env files by cross-checking required credential types extracted from nodes against environment variables. This ensures necessary authentication placeholders are populated locally before attempting import.