smart-reading

Measure unknown file or command output size before reading or delegating to subagents.

8|5|Updated Dec 30, 2025
One-click install
npx skills add https://github.com/axiomantic/spellbook --skill smart-reading
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: smart-reading
Source: https://github.com/axiomantic/spellbook/tree/main/skills/smart-reading
Command: npx skills add https://github.com/axiomantic/spellbook --skill smart-reading

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reading files or command output of unknown size often risks blind truncation, causing context loss and missed insights. This Skill provides a disciplined approach to capture and evaluate content without discarding important information.

Core Features & Use Cases

  • No silent data loss: avoid truncation by measuring size first and choosing an appropriate read strategy.
  • Size-driven reading vs delegation: decide to read the full content or delegate to subagents for targeted summaries.
  • Cleanup discipline: explicit, safe handling of temporary artifacts to prevent resource leaks.

Quick Start

Measure the size of unknown output (e.g., with wc -l) and then either read the full content or delegate analysis accordingly.

Frequently Asked Questions about smart-reading

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

FAQPage Schema
How do I read large log files without truncating the output?

To read large log files without truncating the output, measure the file size first using commands like wc -l, then choose to either read the full content or delegate targeted summaries to subagents.

What is the best way to handle streaming command output of unknown size?

The best way to handle streaming command output of unknown size is applying a size-driven reading strategy that measures the output first, preventing blind truncation and context loss during analysis.

How do I prevent context loss when debugging large reports?

You prevent context loss when debugging large reports by measuring the output size before reading, which ensures explicit data integrity and avoids missing critical insights due to silent truncation.

How to manage temporary artifacts generated during large output analysis?

Manage temporary artifacts generated during large output analysis by applying explicit cleanup discipline, which safely handles and removes temporary files to prevent resource leaks.

When should I delegate command output reading to subagents?

You should delegate command output reading to subagents when the initial size measurement indicates the content is too large for a direct read, allowing targeted summaries without losing full context.

Why does reading unknown-sized command output cause silent data loss?

Reading unknown-sized command output causes silent data loss because standard reads often apply blind truncation, discarding important information and context necessary for debugging and data integrity.