Communityn8ngithub.com

maintain-n8n-workflows

Maintain portable, sanitized, version-compatible n8n workflow templates and their Bootstrap/Maintenance lifecycle. Use when editing or reviewing n8n workflow JSON, moving workflows between instances or n8n versions, grouping agents and subworkflows as one documented project, or preventing scheduled updates from overwriting human documentation.

O que é maintain-n8n-workflows?

maintain-n8n-workflows is a Claude Code agent skill that maintain portable, sanitized, version-compatible n8n workflow templates and their Bootstrap/Maintenance lifecycle. Use when editing or reviewing n8n workflow JSON, moving workflows between instances or n8n versions, grouping agents and subworkflows as one documented project, or preventing scheduled updates from overwriting human documentation.

Funciona com~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/jhvlima/jhvlima-skills/tree/HEAD/skills/maintain-n8n-workflows

Installed? Explore more n8n skills: n8n-workflows, ai-agents-automation, n8n-agent-builder · View all 6 →

Perguntar na sua IA favorita

Abre um novo chat com esta habilidade de agente já pré-carregada.

Documentação

Maintain n8n workflows

Establish the contract

  1. Inspect repository instructions, workflow JSON, export scripts, validators, and the target n8n environment before editing.
  2. Identify the authoritative workflow: live instance, canonical template, or generator output. Edit the authoritative source and regenerate downstream artifacts.
  3. Confirm the requested scope, target n8n version, project grouping rule, and whether the task concerns Bootstrap, Maintenance, or template distribution.
  4. Preserve unrelated local and remote changes. Never infer permission to activate workflows, publish documentation, or mutate a live instance.
  5. Classify the workflow family. Apply the Bootstrap/Maintenance contract only to repositories that implement a documentation lifecycle; do not impose it on unrelated business automation.

Preserve portability and safety

  • Treat workflow IDs, credential IDs, instance URLs, repository coordinates, branch names, and webhook URLs as environment-local values.
  • Replace local references with explicit placeholders or documented post-import selections. Never copy credential material into templates, logs, notes, or examples.
  • Keep project grouping stable with a common documentation tag and a project slug. Represent an agent, its tools, and its called subworkflows as components of one project when they share the same lifecycle.
  • Distinguish sanitizing business workflows from sanitizing the documentation pipeline itself. Apply both checks when publishing templates.
  • Read portability-and-compatibility.md before exporting, importing, or creating a version variant.

Enforce the lifecycle boundary

For a documentation lifecycle:

  • Run Bootstrap once per project to create the deterministic snapshot, optionally enrich human-facing documents with AI, and publish the initial complete file set.
  • Run Maintenance on a schedule or change event to rebuild the deterministic snapshot, compare a functional hash, and publish only technical artifacts when the hash changes.
  • Preserve human-owned documents during Maintenance. Do not invoke AI or overwrite narrative files unless the repository contract explicitly opts into that behavior.
  • Keep the publisher generic: pass exact paths and contents rather than embedding project-specific generation rules.
  • Read lifecycle-contract.md when changing generated paths, ownership, hashing, or orchestration.

Handle version compatibility

  1. Verify the target version instead of assuming compatibility from the source instance.
  2. Compare node types, typeVersion, authentication modes, expression syntax, and required top-level import fields.
  3. Keep one canonical workflow set. Generate a version-specific variant only for demonstrated incompatibilities, and record each transformation without embedding a perishable version as a universal rule.
  4. Require users to reselect local subworkflows and credentials after import when portable placeholders are used.

Validate before handoff

  1. Parse every JSON file and run the repository validator or export checker.
  2. Scan the produced templates for secrets, credential references, local IDs, private URLs, and hard-coded destinations without printing sensitive values.
  3. Test import or dry-run behavior on the declared target version when available.
  4. Exercise Bootstrap for a new project and Maintenance for both unchanged and changed hashes.
  5. Verify that a human edit survives Maintenance and that all subworkflow references resolve after configuration.
  6. Report the authoritative source, generated files, compatibility assumptions, validation evidence, and any manual post-import steps.

Habilidades Relacionadas

n8n-workflows

Find, adapt, and assemble n8n automation workflows from a local library of 2,061 real workflow templates covering 365+ integrations. Use when the user wants to automate something with n8n, asks for an n8n workflow, template, or example, mentions connecting two services with n8n, wants to see how an n8n node is wired up, or needs a starting point for an automation involving webhooks, schedules, or app triggers. Also use when the user asks what n8n can integrate with. Do NOT use for non-n8n automation (Zapier, Make, Airflow) unless the user wants an n8n equivalent.

community

ai-agents-automation

- Build repeatable AI agents and no-code automations with n8n and Zapier: pick the right tool, write the full agent prompt, set up self-hosted n8n, and ship a tested workflow with error handling, cost guards, and a security checklist. Use when automating a repetitive task, building a research or inbox-triage agent, or choosing between n8n, Zapier, and other automation tools.

community

n8n-agent-builder

Build, deploy and manage AI agents on n8n. Use when the user wants an AI agent, chatbot or assistant on n8n - with its own chat page or website widget, on WhatsApp, Telegram, Slack or as an API - connected to any LLM (OpenAI, Claude, Gemini, Groq, Mistral, Ollama, OpenRouter or any OpenAI-compatible API), optionally answering from their documents (RAG), using tools (Google Sheets, Calendar, Gmail, web search, Shopify, WooCommerce, HubSpot, databases, MCP), or routing to specialist sub-agents. Also for updating, testing, listing or deleting such agents.

community

ashtonfeliciano/n8n-workflow-engineer

Build, debug, and harden n8n workflows. Use when the user is editing n8n workflow JSON, debugging silent failures, working with Code nodes, Telegram / Gmail / HTTP Request nodes, scheduled triggers, paired-item tracking, dedup with static data, or doing bulk operations via the n8n REST API. Covers v2.x UI specifics. Not for non-n8n automation.

community

ashtonfeliciano/n8n-evaluations-runner

Build and run zero-API-cost logic test suites for n8n workflows. Use when adding test coverage to filter logic, scoring functions, validators, keyword lists, resume maps, or any pure-JS code-node logic. Outputs grouped pass/fail/pending report via Telegram. Run before AND after any logic change to catch regressions without burning API credits.

community

caiqueDeOliveira-dev/homelab

HomeLab Agent — Gerencia Home Assistant, ESP32 satellites, dispositivos Zigbee/Matter/Thread, automações físicas, cameras, sensores. Camada de decisão e execução no hardware (não orquestração de software = Automação/n8n).

community