Agent skill · Data & Analytics

n8n-binary-and-data

Handle n8n files and binary data across uploads, downloads, transforms, multimodal inputs, agent tools, and chat surfaces.

Nick44,086★ · +407/wk · 1 repos on radarProfile →
claude-codecodexcursorMIT
Install
npx skills add sickn33/agentic-awesome-skills --skill n8n-binary-and-data --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 5
SKILL.md size: 16 KB
Bundled scripts: none
Declared author: Romuald Czlonkowski
Path: skills/n8n-binary-and-data/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 44,414 · +328 this week
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# n8n Binary and Data ## When to Use Use this skill when an n8n workflow reads, transforms, stores, uploads, downloads, or transmits files and binary fields, including multimodal agent inputs and chat attachments. Treat uploaded files and generated URLs as potentially sensitive. Obtain approval before sending data to a new external host, use the narrowest retention and access scope available, avoid logging bytes or base64 payloads, and do not embed credentials in URLs or workflow fields. Every n8n item carries two independent slots: `$json` for structured data and `$binary` for file bytes. They travel side by side through the workflow. File contents — the actual PDF, image, or zip — live in `$binary`, never in `$json`. Get that split wrong and you read an empty field, lose a file mid-flow, or hand an AI agent a tool input it can't use. This skill covers where binary lives, how to read and write it, how to keep it from being silently stripped, the hard wall between binary and the AI-agent tool boundary, and why chat surfaces need a URL instead of raw bytes. --- ## The three rules that prevent 90% of binary bugs 1. **File contents are in `$binary`, not `$json`.** After an HTTP downlo

What's inside
Steps it walks through
  1. When to Use
  2. The three rules that prevent 90% of binary bugs
  3. The two slots
  4. Producing binary
  5. Reading and writing binary in a Code node
  6. Keeping binary alive across transforms
  7. The agent-tool binary boundary
  8. The CDN requirement for chat surfaces
  9. What's NOT available
  10. Where Data Tables live
  11. Anti-patterns
  12. Reference files
  13. Integration with Other Skills
  14. Verifying binary survived
Ships with 4 files
  • references/AGENT_TOOL_BINARY.md
  • references/BINARY_BASICS.md
  • references/CDN_REQUIREMENT.md
  • references/MERGE_FOR_CONTEXT.md
More from agentic-awesome-skills
All skills →
About this skill
What does the n8n-binary-and-data skill do?

Handle n8n files and binary data across uploads, downloads, transforms, multimodal inputs, agent tools, and chat surfaces.

How do I install it?

Run `npx skills add sickn33/agentic-awesome-skills --skill n8n-binary-and-data --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From sickn33/agentic-awesome-skills, a repository with 44,414 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going