n8n-binary-and-data

Handle files and binary data in n8n correctly. Use when working with files, images, PDFs, attachments, uploads or downloads, base64, vision/multimodal input, or when an AI agent needs a file as tool input or output — and whenever the user mentions $binary, binaryPropertyName, "read the PDF", "attach the file", "send the image", Merge losing binary, or a CDN for chat images. Covers the $binary vs $json split, reading/writing binary, keeping binary alive across transforms with Merge, the agent-tool binary boundary, and the CDN/URL requirement for chat surfaces.

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Quality

Content

88%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A strong, actionable body with executable code, explicit validation feedback loops, and clean reference signaling. The only gap is that the four referenced .md files are not present in the bundle to confirm progressive disclosure lands on real files.

Suggestions

Ship the referenced bundle files (BINARY_BASICS.md, AGENT_TOOL_BINARY.md, MERGE_FOR_CONTEXT.md, CDN_REQUIREMENT.md) under ./references/ so the 'See <file>.md' pointers resolve to real content.

Trim the motivational opener and the closing 'Remember' line; the three-rules section and Quick Reference Checklist already carry that messaging more compactly.

Consider moving the 'What's NOT available' and 'Anti-patterns' tables into BINARY_BASICS.md to slim the SKILL.md overview further while keeping them one click away.

Dimension	Reasoning	Score
Conciseness	Dense and n8n-specific throughout with no generic 'what a PDF is' padding, but ~245 lines include some motivational prose (e.g. the 'Get that split wrong...' opener and the closing 'Remember' line) that slightly overlaps the checklist and could be trimmed.	4 / 5
Actionability	Copy-paste-ready Code-node snippets (getBinaryDataBuffer, Buffer.from(...).toString('base64')), named parameters (responseFormat, binaryPropertyName, includeOtherFields, binaryPropertyOutput, combineByPosition, passthroughBinaryImages), and a concrete numbered inbound/outbound staging pattern fully cover the common cases.	5 / 5
Workflow Clarity	Multi-step inbound/outbound agent-tool flows are numbered with an explicit synchronization barrier and executeOnce guard for batch uploads, plus a 'Verifying binary survived' feedback loop (test → n8n_executions → inspect binary slot → fix at the strip point) and a Quick Reference Checklist.	5 / 5
Progressive Disclosure	Excellent signaling — a 'Reference files' table maps BINARY_BASICS.md, AGENT_TOOL_BINARY.md, MERGE_FOR_CONTEXT.md, CDN_REQUIREMENT.md to 'Read when' triggers and references are one level deep — but no ./references bundle directory exists, so the referenced files cannot be verified as present.	4 / 5
	Total	18 / 20 Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

An exemplar description: third-person voice, concrete actions, exhaustive natural trigger terms, and explicit what/when guidance scoped tightly to n8n binary handling. No vague fluff or over-claims.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'reading/writing binary', 'keeping binary alive across transforms with Merge', 'the agent-tool binary boundary', and 'the CDN/URL requirement for chat surfaces' — covering the domain comprehensively.	5 / 5
Completeness	Explicitly answers both what ('Handle files and binary data in n8n correctly... Covers the $binary vs $json split...') and when ('Use when working with files, images, PDFs... or when an AI agent needs a file as tool input or output — and whenever the user mentions $binary...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Comprehensive natural-term coverage including synonyms and quoted user phrases: 'files, images, PDFs, attachments, uploads or downloads, base64, vision/multimodal input' plus 'read the PDF', 'attach the file', 'send the image', and '$binary', 'binaryPropertyName'.	5 / 5
Distinctiveness Conflict Risk	Clear n8n-specific niche with distinctive triggers ($binary, binaryPropertyName, 'Merge losing binary', 'CDN for chat images') that would not fire for unrelated skills; minimal conflict risk.	5 / 5
	Total	20 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: czlonkowski/n8n-mcp
Path: data/skills/n8n-binary-and-data/SKILL.md
Commit: fe3a4cb

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.