Agent skill · data analytics · n8n-io
data-table-manager
Load before calling data-tables or parse-file. Use for natural standalone requests like "what data tables do I have?", "show/list my tables", or "what columns are in this table?", and whenever the user asks to list, show, create, inspect, import, seed, query, update, clean up, rename columns in, or delete data tables and rows, especially from CSV/XLSX/JSON attachments. Also load before building or planning workflows that create or write to Data Tables (then load workflow-builder before build-workflow).
Why this skill is useful
Provides specific commands and procedures for managing n8n Data Tables that the AI wouldn't reliably generate on its own.
What it needs
Requires data-tables, parse-file installed locally. About 6k tokens when loaded. Last updated 2026-08-07. 199,638 stars on the source repository.
What this skill does
Data Table Manager Routing For workflow builds that create or write Data Tables, load this skill, then workflow-builder, before build-workflow. Use this skill to build and maintain n8n Data Tables in the current turn with data-tables and, for attachments, parse-file. Do not spawn another agent or create a background plan for data-table-only work. Also load this skill before planning or building a workflow whose trigger, processing steps, or outputs create, inspect, or write Data Table records, then pass the relevant schema/row-handling guidance to the planning skill or builder. n8n Data Tables are flat, workflow-friendly stores. Design them so future workflow expressions can read predictable field names and so updates/deletes can target rows with narrow filters. Default Procedure 1. Classify the job: inspect, design/create, import, seed, query, schema change, row mutation, row delete, table delete, or cleanup. 2. Resolve the target first. Call data-tables(action="list") before creating a table, acting on a table name, or choosing a project. If there is more than one plausible match, ask one concise clarification. 3. Use table IDs after discovery. Include projectId whenever list results or the user identify a project. Pass dataTableName on mutating calls when you know it so approval cards show a recognizable label. 4. Inspect schema before writes, deletes, column changes, imports into an existing table, and workflow-facing summaries. 5. Execute the smallest direct tool sequence. Prefer read -> decide -> write; never use create-tasks for standalone table work. 6. Close with facts: table name, table ID when available, project if relevant, columns changed, row counts inserted/updated/deleted, skipped rows, and any approval or permission blocker. Design Rules Use stable lowercase snakecase column names: customeremail, ordertotal, processedat. Data Tables accept alphanumeric names and underscores; avoid spaces, punctuation, and display-only labels. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills n8n-io/data-table-manager