file-reading

Route uploaded files to appropriate readers based on metadata and extension.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/michaelkd01/dic-skills --skill file-reading
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: file-reading
Source: https://github.com/michaelkd01/dic-skills/tree/main/_public/file-reading
Command: npx skills add https://github.com/michaelkd01/dic-skills --skill file-reading

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Uploaded files often appear only as paths in /mnt/user-data/uploads, and blindly catting them floods your context, mangles binaries, or crashes tools. This skill ensures you pause, inspect the metadata, and choose the right reader so every file is handled safely before you or another skill consumes its contents.

Core Features & Use Cases

  • Extension-aware routing: The dispatch table maps extensions to the correct first move or dedicated skill whether it is pdf, docx, xlsx, pptx, csv, json, archives, ebooks, images, or plain text.
  • Safe probing guidance: Encourages stat/file inspection and sampling techniques to understand size, format, and readability before importing anything.
  • Seamless handoffs: When a specialized skill exists (PDF, DOCX, XLSX, PPTX), it directs you there so you never overwrite the guarded sandbox protocols for conversion or detailed editing.

Quick Start

Ask the skill to inspect the uploaded file path, determine its extension, and point you to the appropriate reader before loading any data.

Frequently Asked Questions about file-reading

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I handle uploaded files safely without crashing my context?

Safe file handling requires inspecting metadata and extensions before reading uploads. This routing skill dispatches each file to the correct reader, ensuring binary and large files are processed safely without crashing tools or flooding context.

What's the best way to read PDF and DOCX files from upload paths?

Reading PDF and DOCX files safely requires extension-aware routing to dispatch them to dedicated skills. This approach maintains guarded sandbox protocols for conversion and editing, preventing data corruption when processing uploads from file paths.

Why does reading binary files directly from /mnt/user-data/uploads cause problems?

Reading binary files directly causes problems because blindly catting them mangles binary data, floods your context window, or crashes tools. Inspecting file metadata and characteristics first ensures safe dispatching to the appropriate reader.

Can I use this file routing approach for CSV, JSON, and spreadsheet uploads?

Yes, this routing approach supports CSV, JSON, and spreadsheet uploads. The dispatch table maps these extensions to the correct first move, ensuring structured data files are handled safely before consuming their contents.

Does this file dispatcher work with archives, ebooks, and image formats?

Yes, this file dispatcher works with archives, ebooks, and images. The extension-aware routing table covers these formats, ensuring safe probing and metadata inspection before loading binary or large image data into context.

When should I inspect file metadata before reading uploaded data?

You should inspect file metadata before reading uploaded data whenever a file path appears in /mnt/user-data/uploads. This precaution ensures you understand size, format, and readability, allowing safe dispatch to the correct reader.