list-workflows

Scan /workflows directory and summarize n8n workflow metadata and credentials.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of not knowing what n8n workflows exist in a repository and which ones are ready to run locally, so you can plan imports and configuration efficiently.

Core Features & Use Cases

  • Workflow directory inventory: Scans /workflows and identifies valid n8n workflow JSON files while ignoring unrelated files.
  • Per-workflow metadata extraction: Pulls each workflow’s name, node count, webhook endpoints, credential types needed, file size, and last modified date.
  • Optional import status checking: If the local n8n server is reachable at http://localhost:5678, compares repository workflows to what is already imported and reports ✓ imported vs ✗ not imported.
  • Summary table output: Presents a clean table plus a consolidated credential overview and recommended next imports.

Quick Start

Ask the assistant: “List all n8n workflows in this Cyclone-SS repository and show their metadata, including webhook endpoints, required credentials, and which are already imported in local n8n.”

Frequently Asked Questions about list-workflows

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

FAQPage Schema
How do I inventory all n8n workflows in a repository?

Scanning a repository's /workflows directory identifies valid n8n workflow JSON files and extracts metadata like node counts, webhook endpoints, required credentials, file sizes, and last modified dates into a consolidated summary table for planning imports.

What n8n workflow metadata can I extract without importing the files?

You can extract workflow name, node count, webhook endpoints, required credential types, file size, and last modified date directly from workflow JSON files. For large files, parsing partial content captures essential metadata without requiring a full n8n import.

How do I check if n8n workflows are already imported in my local server?

Checking n8n workflow import status requires a reachable local n8n server at http://localhost:5678. The process compares repository workflow definitions against the local instance and reports which are already imported versus pending configuration.

Can I check which credentials are needed across all my n8n workflows?

Scanning workflow JSON files across the repository extracts required credential types for each n8n workflow. The resulting summary table presents a consolidated credential overview, allowing you to verify local readiness and plan configuration for webhook-driven automation.

Does this workflow inventory approach handle large n8n JSON files?

Yes, the inventory process handles large n8n JSON files by parsing partial content. Instead of loading entire files, it reads only the necessary sections to capture workflow metadata, ensuring efficient repository-wide scanning for valid workflow definitions.