Wagner-Emden-IT-Services
Organizationn8n-Workflow-Template mit Cross-Platform Node-CLI, Hybrid-Naming, Drift-Detection, verifiziertem Auto-Rollback und Disaster-Recovery. Optimiert fuer Claude Code.
Categories
Indexed Skills (17)
qa-workflow
QA-Verifikation fuer n8n-Workflows — Test-Run via mcp__n8n__validate_workflow + manuell, Severity-Heuristik P0-P3, Auto-File P0/P1 als GitHub-Issues, User-Choice P2/P3.
handoff
Compact the current conversation into a handoff document for another agent to pick up. Use at session end or between pipeline phases when the work continues in a fresh session.
diagnosing-bugs
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
domain-modeling
Build and sharpen a project's domain model. Use when the user wants to pin down domain terminology or a ubiquitous language, record an architectural decision, or when another skill needs to maintain the domain model.
n8n-code-javascript
Write JavaScript code in n8n Code nodes. Use when writing JavaScript in n8n, using $input/$json/$node syntax, making HTTP requests with $helpers, working with dates using DateTime, troubleshooting Code node errors, choosing between Code node modes, or doing any custom data transformation in n8n. Always use this skill when a workflow needs a Code node — whether for data aggregation, filtering, API calls, format conversion, batch processing logic, or any custom JavaScript. Covers SplitInBatches loop patterns, cross-iteration data, pairedItem, and real-world production patterns.
n8n-code-python
Write Python code in n8n Code nodes. Use when writing Python in n8n, using _input/_json/_node syntax, working with standard library, or need to understand Python limitations in n8n Code nodes. Use this skill when the user specifically requests Python for an n8n Code node. Note — JavaScript is recommended for 95% of use cases — only use Python when the user explicitly prefers it or the task requires Python-specific standard library capabilities (regex, hashlib, statistics).
n8n-expression-syntax
Validate n8n expression syntax and fix common errors. Use when writing n8n expressions, using {{}} syntax, accessing $json/$node variables, troubleshooting expression errors, mapping data between nodes, or referencing webhook data in workflows. Use this skill whenever configuring node fields that reference data from previous nodes — expressions are how n8n passes data between nodes, and getting the syntax wrong is the most common source of workflow errors.
n8n-mcp-tools-expert
Expert guide for using n8n-mcp MCP tools effectively. Use when searching for nodes, validating configurations, accessing templates, managing workflows, managing credentials, auditing instance security, or using any n8n-mcp tool. Provides tool selection guidance, parameter formats, and common patterns. IMPORTANT — Always consult this skill before calling any n8n-mcp tool — it prevents common mistakes like wrong nodeType formats, incorrect parameter structures, and inefficient tool usage. If the user mentions n8n, workflows, nodes, or automation and you have n8n MCP tools available, use this skill first.
n8n-node-configuration
Operation-aware node configuration guidance. Use when configuring nodes, understanding property dependencies, determining required fields, choosing between get_node detail levels, or learning common configuration patterns by node type. Always use this skill when setting up node parameters — it explains which fields are required for each operation, how displayOptions control field visibility, and when to use patchNodeField for surgical edits vs full node updates.
n8n-prd-generator
Generate structured PRD documents for n8n automation workflows. Use when planning n8n workflows, creating automation requirements, starting a new n8n project, or preparing workflow specifications before building.
n8n-validation-expert
Interpret validation errors and guide fixing them. Use when encountering validation errors, validation warnings, false positives, operator structure issues, or need help understanding validation results. Also use when asking about validation profiles, error types, the validation loop process, or auto-fix capabilities. Consult this skill whenever a validate_node or validate_workflow call returns errors or warnings — it knows which warnings are false positives and which errors need real fixes.
n8n-workflow-patterns
Proven workflow architectural patterns from real n8n workflows. Use when building new workflows, designing workflow structure, choosing workflow patterns, planning workflow architecture, or asking about webhook processing, HTTP API integration, database operations, AI agent workflows, batch processing, or scheduled tasks. Always consult this skill when the user asks to create, build, or design an n8n workflow, automate a process, or connect services — even if they don't explicitly mention 'patterns'. Covers webhook, API, database, AI, batch processing, and scheduled automation architectures.
n8n-workflow-reviewer
Reviews n8n workflows for errors, inefficiencies, and missing best practices. Use this skill whenever a user shares an n8n workflow JSON, describes their workflow setup, pastes node configurations, or asks questions like "can you review my workflow", "what's wrong with my n8n automation", "how can I improve this workflow", "why is my n8n workflow failing", or "check my n8n setup". Trigger even when the user only shares a partial workflow, a single node config, or describes their workflow in plain text — any n8n review or debugging request should use this skill. In this template, ALSO invoke this skill automatically right after building or modifying ANY workflow JSON (post-build review) — before validation, security-review and deploy — not only when the user explicitly asks for a review.
grill-me
A relentless interview to sharpen a plan or design.
grilling
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking — including stress-testing PRDs, WF-X specs, or workflow designs — or uses any 'grill' trigger phrases.
research
Investigate a question against high-trust primary sources and capture the findings as a Markdown file in the repo. Use when the user wants a topic researched, docs or API facts gathered, or reading legwork delegated to a background agent.
grill-with-docs
A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go. Use at the start of the Spec phase when requirements for a new workflow are unclear or ambiguous.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.