filesystem-context

Manage agent context by offloading tool outputs and persisting state to files.

Updated Nov 13, 2025
One-click install
npx skills add https://github.com/466852675/TISHICIKU-2025 --skill filesystem-context-466852675
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: filesystem-context
Source: https://github.com/466852675/TISHICIKU-2025/tree/main/07-Skill%E5%BA%93/filesystem-context
Command: npx skills add https://github.com/466852675/TISHICIKU-2025 --skill filesystem-context-466852675

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill addresses the limitations of fixed context windows by enabling agents to dynamically manage and retrieve information from the filesystem, effectively providing an unlimited memory.

Core Features & Use Cases

  • Context Offloading: Store large tool outputs or intermediate results in files to prevent context window bloat.
  • Persistent State: Save agent plans, learned preferences, or sub-agent communications to files for long-term memory.
  • Dynamic Discovery: Use file search tools (grep, glob) to retrieve specific information on demand, rather than loading everything at once.
  • Use Case: An agent processing a large web search result can offload the raw HTML to a file, then use grep to extract only the relevant product details, keeping the context window clean and focused.

Quick Start

Use the filesystem-context skill to save the output of the 'web_search' tool to a file.

Frequently Asked Questions about filesystem-context

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

FAQPage Schema
How do I manage unlimited context for an agent when the context window is full?

To manage unlimited context, you can offload large tool outputs to the filesystem and use search tools like grep to retrieve specific information dynamically, preventing context window bloat.

How does filesystem-based agent memory work for persisting state?

Filesystem-based agent memory works by writing plans, learned preferences, and sub-agent communications to files, allowing the agent to retrieve and reload this persistent state on demand.

Can I use grep and glob to dynamically load context into an agent?

Yes, you can use file search tools like grep and glob for dynamic context discovery, retrieving specific information from the filesystem on demand rather than loading everything into the context window at once.

What is the best way to store large web search results without exceeding agent context limits?

The best way to store large web search results is to offload the raw HTML or tool output to a file, then use grep to extract only the relevant details, keeping the agent's context window clean and focused.

Does this approach support scratch pads and sub-agent communication patterns?

Yes, this approach supports scratch pads, plan persistence, and sub-agent communication by leveraging file operations to save and retrieve intermediate results and persistent state across the filesystem.

When should I not use filesystem context management for an agent?

You should avoid filesystem context management if your agent environment lacks file operation capabilities or if your task requires keeping all data strictly in memory without filesystem persistence.