Use when building n8n AI Agent / LangChain clusters — tools, memory, RAG, structured output, system prompts, sub-workflow-as-tool, or fixing agent connection topology (ai_languageModel, ai_tool, ai_memory).
Use when building n8n workflows for SEO, AEO, GEO, AI visibility monitoring, content pipelines, schema/JSON-LD checks, rank/citation tracking, or integrating Molavi GEO tools (geo-scope, mcp-geo-server) with n8n.
Use when considering a Code node, writing JavaScript/Python in n8n, fixing Code return shape errors, or deciding between expression, Edit Fields, and Code.
Use whenever auth, API keys, OAuth, tokens, secrets, or credential setup appears in n8n work. Enforces credential system usage, least privilege, and safe HTTP auth patterns.
Use when designing or querying n8n Data Tables for durable state, deduplication, checkpoints, lightweight CRM-like storage, or idempotency keys inside workflows.
Use when n8n workflows fail, return empty data, drop items silently, show expression errors, or when diagnosing executions with MCP explain/timeline tools.
Use for production n8n workflows, webhook APIs, retries, error outputs, error workflows, dead-letter patterns, and correct HTTP response status shapes for callers.
Use when writing or debugging n8n expressions (`{{ }}`), `$json`, `$('Node')`, `$input`, Luxon/DateTime, field mapping, or "expression error" / wrong data after Merge.
Use for batching, pagination, "for each", Loop Over Items, Split Out, Aggregate, rate limits, or processing arrays in n8n. Default per-item execution often removes the need for an explicit loop node.
Use when configuring n8n MCP servers, choosing tools across official and community MCPs, routing generate/lint/explain/CRUD calls, or debugging MCP auth. Covers official instance MCP, AutomateLab, czlonkowski, salacoste, leonardsellem.
Use when configuring any n8n node parameters — HTTP Request, Webhook, triggers, Merge, Switch/IF, databases, spreadsheets, AI sub-nodes. Never guess typeVersion or property dependencies; load live schema first.
Use for multi-environment n8n setups, backups, CI lint of workflow JSON, activation policy, secrets rotation, observability, and safe promotion from staging to production.
Use when extracting reusable n8n logic, multi-step builds, sub-workflow triggers, tagging for discovery, passthrough vs Define Below inputs, or exposing workflows as agent tools.
Use when starting, designing, organizing, validating, testing, publishing, or handing off any n8n workflow. Covers naming, folders/projects, sticky notes, validation vs verification, side-effect-aware testing, and production handoff.
Use when working with n8n workflows in any capacity. Always-on meta-skill and router for the Molavi n8n-agent-skills pack. Routes to capability skills, summarizes MCP tool families across official and community servers, and lists non-negotiable cross-cutting rules.
A folder with a SKILL.md file: a name, a description of when to use it, and instructions. Claude loads a skill only when the task matches its description.
How do I use one I find here?
Copy the folder into your project's .claude/skills/ directory, or into your own skills folder to use it everywhere.
What do the warnings mean?
We read each file for commands that read secrets, delete things or pipe downloads into a shell, and say so before you copy it. No warning is not a promise that a file is safe.
Which skills worked for people?
Open a skill to see its discussion. Reports from people and their agents are coming.