file-read-skill

Read local files with line-numbered output and offset/limit pagination.

356|66|Updated Oct 13, 2025
One-click install
npx skills add https://github.com/zeenie-ai/MachinaOS --skill file-read-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: file-read-skill
Source: https://github.com/zeenie-ai/MachinaOS/tree/main/server/skills/coding_agent/file-read-skill
Command: npx skills add https://github.com/zeenie-ai/MachinaOS --skill file-read-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of quickly inspecting local files by returning readable, line-numbered content without overwhelming the AI with entire large files.

Core Features & Use Cases

  • Line-numbered output: Returns file content with tab-separated line numbers for precise referencing.
  • Pagination support: Uses offset and limit so large files can be read in chunks (e.g., logs, generated code, long configs).
  • Binary handling: Returns base64-encoded content for binary files so the content is still accessible when needed.

Use Case: If you are debugging a failing component and need to inspect only the relevant section of a large log or source file, you can request just the lines around the error.

Quick Start

Ask the AI to read /path/to/your/app.log starting at offset 0 with a limit of 200 lines.

Frequently Asked Questions about file-read-skill

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

FAQPage Schema
How do I read a large log file in chunks with line numbers?

To read a large log file in chunks with line numbers, use pagination by specifying an offset and limit. This returns tab-separated, line-numbered content for the requested segment, preventing the large file from overwhelming the AI context.

What is the best way to inspect specific source code lines during debugging?

The best way to inspect specific source code lines during debugging is to request targeted file segments with line numbers. By setting an offset and limit, you retrieve only the relevant section around the error for precise code inspection.

Can I read binary files and get their content without corruption?

Yes, you can read binary files and retrieve content without corruption. The filesystem backend returns base64-encoded content for binary files, ensuring the data remains accessible and intact for your inspection workflow.

Does file reading support offset and limit for configuration inspection?

Yes, file reading supports offset and limit for configuration inspection. These pagination parameters allow you to read long configuration files in manageable chunks, returning line-numbered output for precise referencing.

What happens when I try to read an entire large generated code file?

When you read an entire large generated code file, you risk overwhelming the AI context. Instead, apply offset and limit parameters to retrieve line-numbered segments, making targeted code review and debugging more efficient.

Why are line numbers useful for log examination?

Line numbers are useful for log examination because they provide precise referencing through tab-separated output. This allows you to pinpoint exact error locations and communicate them clearly during debugging and code review.