en un clic
n8n-cli
n8n-cli contient 40 skills collectées depuis 8Dvibes, avec une couverture métier par dépôt et des pages de détail sur le site.
Skills dans ce dépôt
Back up an entire n8n instance to a git-tracked directory. Exports all workflows, credentials, tags, and variables as a snapshot. NOT single-file export -- use /n8n-export for that. Use when creating full instance snapshots.
Run bulk activate/deactivate/archive/transfer operations across n8n workflows with mandatory dry-run first. Operates on existing tags -- NOT tag design (use /n8n-cli-tag-governance). Use for batch state changes and project reorgs.
Find dead workflows, orphaned credentials, and duplicate webhooks for deletion. Outputs safe-to-delete recommendations. NOT tagging -- use /n8n-cli-tag-governance for that. Use for quarterly hygiene sweeps.
Analyze n8n execution costs and usage patterns. Finds top consumers, hourly distribution, and triggers firing too often. Use when investigating high usage, before billing reviews, or optimizing execution counts.
Build an n8n workflow from an English description. Generates valid JSON and imports it via n8n-cli. Use when creating a new workflow from scratch based on a natural-language spec.
Audit n8n credentials and find gaps. Lists what exists, what workflows need, and what is missing. Use when auditing credentials, setting up new workflows, or troubleshooting auth failures.
Analyze failed n8n executions and suggest fixes. Pulls error logs, groups by pattern, and diagnoses root causes. NOT replay -- use /n8n-cli-replay to re-run a specific failure. Use when debugging workflow errors.
Map n8n workflow dependencies as a graph. Shows sub-workflow calls, credential refs, and webhook URLs as tree, mermaid, or JSON. Use when understanding interconnections before making changes.
Diff n8n workflow versions side-by-side. Shows structural changes between instances, local files, or backups. NOT a review -- use /n8n-cli-review for risk analysis. Use when checking for drift or auditing what changed.
Generate human-readable markdown docs from an n8n workflow JSON. Covers trigger, steps, credentials, and failure modes. Use when documenting workflows for team handoff, audits, or onboarding.
Export individual n8n workflows to JSON files. Selective, single-workflow exports for git or sharing. NOT a full instance backup -- use /n8n-backup for that. Use when saving one workflow to a file.
Convert crontab entries into equivalent n8n workflows. Reads cron jobs and generates one workflow per entry. Use when migrating off bare cron onto n8n for visibility and error handling.
Convert macOS launchd plists into equivalent n8n workflows. Reads LaunchAgents and LaunchDaemons. macOS sibling to /n8n-cli-from-cron. Use when migrating off launchd onto n8n for observability.
Convert an MCP server or Claude Code skill into an n8n workflow. Moves agent capabilities into n8n to run on a schedule or webhook without an agent. Use when productizing an MCP-driven prototype.
Migrate a Zapier zap to an equivalent n8n workflow. Reads zap exports or descriptions and generates n8n JSON. Use when moving off Zapier for cost, ownership, or flexibility.
Check blast radius before making n8n changes. Answers 'if I delete credential X or deactivate workflow Y, what breaks?' Use before any destructive operation in production.
Import n8n workflow JSON with guided credential mapping. Resolves credential references during import. Use when loading workflows from files, repos, or other instances into n8n.
Build a self-monitoring workflow inside n8n that alerts on failures via Slack/Discord/email. Creates an actual n8n workflow -- NOT a CLI watcher (use /n8n-monitor for that). Use when setting up always-on observability.
Migrate n8n workflows between instances (cloud to self-hosted or vice versa). Exports, remaps credentials, and imports in one pass. Use when moving workflows across n8n environments.
Poll n8n execution stream from the terminal and surface failures. Runs outside n8n as a CLI watcher. NOT a workflow -- use /n8n-cli-meta-monitor to build an in-n8n alerting workflow. Use when watching for errors live.
Search all n8n workflows for a specific node type, credential, or pattern. Answers 'which workflows use Slack?' Use when an API changes, a node has a breaking update, or you need to find every use of a service.
Refactor an n8n workflow for simplification. Finds redundant nodes, batching opportunities, and over-complex Code nodes, then proposes a cleaner version. Use when a workflow feels unwieldy or has grown past 20 nodes.
Replay a specific failed n8n execution with its original input data. Reproduces the failure on demand without waiting for the trigger. NOT pattern analysis -- use /n8n-debug for that. Use when reproducing an intermittent bug.
Review n8n workflow changes PR-style with risk ratings. Explains what changed, why it matters, and flags dangers. NOT a raw diff -- use /n8n-diff for that. Use when approving changes before production or after a handoff.
Audit n8n Schedule Triggers for cron collisions and bad expressions. Finds 50-things-at-3am pileups and suggests rebalanced schedules. Use before going to production, after imports, or when spreading load.
Run smoke tests against n8n webhook workflows. Sends known-good payloads and verifies expected responses. Use when promoting to production, after major changes, or as a daily reliability check.
Check n8n instance health, active workflows, and recent execution stats. Quick overview in one command. Use when checking if n8n is up, reviewing status, or getting an instance summary.
Design and enforce a tag taxonomy for n8n workflows. Finds untagged workflows, proposes tags based on content, and applies them. NOT deletion -- use /n8n-cli-cleanup for junk removal. Use when tagging is inconsistent or missing.
Templatize or instantiate n8n workflows. Strips IDs and credentials to create reusable templates, or fills placeholders to create new workflows from templates. Use for sharing patterns across instances or building a library.
Generate realistic test payloads for n8n webhook workflows. Infers input schema and creates happy-path, edge-case, and error fixtures. Use when adding tests to an existing workflow or building one TDD-style.
Expose an n8n workflow as an MCP tool for AI agents. Generates a tool definition that Claude, Cursor, or Codex can call. Inverse of /n8n-cli-from-mcp. Use when agents need to invoke an n8n workflow on demand.
Pre-flight safety check before upgrading n8n. Scans for deprecated nodes, breaking changes, and at-risk community packages. Outputs a go/no-go report. Use before any major n8n version bump.
Fire test requests at n8n webhook endpoints from the terminal. Sends custom or empty payloads and shows the response. Use when testing webhooks, debugging integrations, or verifying triggers.
Write JavaScript in n8n Code nodes. Covers $input/$json/$node syntax, $helpers HTTP requests, DateTime, error patterns, and run-once vs run-for-each modes. Use when writing or fixing JS inside n8n.
Write Python in n8n Code nodes (beta). Covers _input/_json/_node syntax and stdlib-only constraints. JS is preferred for 95% of cases. Use only when Python stdlib functions are specifically needed in n8n.
Validate and fix n8n expression syntax. Covers {{ }} double-brace syntax, $json/$node variables, and common mistakes. NOT Code node JS -- use /n8n-code-javascript for that. Use when debugging expressions.
Guide for using n8n-mcp MCP server tools effectively. Covers tool selection, parameter formats, node search, config validation, and template access. Use when invoking any n8n-mcp MCP tool.
Configure n8n nodes with operation-aware property guidance. Covers required fields, property dependencies, and detail levels per node type. Use when setting up node parameters or understanding which fields an operation needs.
Fix n8n workflow validation errors. Interprets error codes, identifies false positives, and guides fixes for operator structure issues. Use when a workflow fails validation or you need to understand validation profiles.
Reference library of proven n8n workflow architecture patterns. Covers webhooks, HTTP APIs, database ops, AI agents, and scheduled tasks. Use when designing workflow structure or choosing a pattern for a new build.