filesystem-context

Offload agent context to filesystem files for dynamic retrieval and persistence.

Updated Apr 17, 2026
One-click install
npx skills add https://github.com/Syedyasir001/RVULibPass --skill filesystem-context-syedyasir001
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: filesystem-context
Source: https://github.com/Syedyasir001/RVULibPass/tree/main/.agent/skills/library/filesystem-context
Command: npx skills add https://github.com/Syedyasir001/RVULibPass --skill filesystem-context-syedyasir001

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? LLM context windows are limited, and large tool outputs, long-running plans, and multi-agent communication quickly bloat or overflow the window. This Skill uses the filesystem as an overflow layer so agents store, retrieve, and update context on demand instead of keeping everything in the prompt. ## Core Features & Use Cases - Tool Output Offloading: Write large tool outputs to scratch files and return compact summaries with file references, keeping only ~100 tokens in context. - Plan Persistence: Save structured plans (JSON/YAML) to disk so agents can re-read objectives and progress after context refreshes or summarization. - Sub-Agent Workspaces & Dynamic Skill Loading: Route sub-agent findings through isolated file directories and load full skill files only when relevant, converting O(n) static token cost into O(1) per task. - Use Case: A web search returns 8000 tokens; the agent writes it to scratch/search_results_001.txt, returns a one-line summary, and greps the file later for specific details. ## Quick Start Ask the agent to offload large tool outputs to scratch files and persist the current plan to disk so it can re-read them on demand.

Frequently Asked Questions about filesystem-context

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

FAQPage Schema
How do I reduce LLM context window bloat from tool outputs?▼

Write large tool outputs to scratch files and return a compact summary with a file reference instead of the full content. The agent then uses grep or line-range reads to retrieve only the sections it needs, keeping roughly 100 tokens in context.

How to persist agent plans across context window refreshes?▼

Serialize the plan as structured JSON or YAML to a file like scratch/current_plan.json, including objective, step statuses, and notes. The agent re-reads the file at the start of each turn or after summarization to restore task awareness.

When should I use filesystem-based context management?▼

Use it when tool outputs exceed roughly 2000 tokens, tasks span multiple turns, or multiple agents share state. Avoid it for single-turn tasks, when context fits comfortably, or when file I/O latency is unacceptable.

Can sub-agents share information through files instead of messages?▼

Yes, each sub-agent writes findings to its own isolated workspace directory, and the coordinator reads those files directly. This avoids the summarization degradation that occurs in multi-hop message passing.

What are the risks of agent scratch pad files?▼

Scratch directories grow unbounded without cleanup, concurrent writes can corrupt shared files, and stale paths break after renames. Apply retention policies, per-agent directory isolation, and existence checks before reading cached paths.