filesystem-context

Offload large tool outputs to filesystem files for dynamic context loading.

947|163|Updated Jan 13, 2026
One-click install
npx skills add https://github.com/guanyang/antigravity-skills --skill filesystem-context-guanyang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: filesystem-context
Source: https://github.com/guanyang/antigravity-skills/tree/main/skills/filesystem-context
Command: npx skills add https://github.com/guanyang/antigravity-skills --skill filesystem-context-guanyang

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill addresses the fundamental limitation of fixed context windows by enabling agents to leverage the filesystem for effectively unlimited memory and dynamic context discovery.

Core Features & Use Cases

  • Offload Large Outputs: Persist massive tool outputs (e.g., search results, logs) to files, keeping the context window clean and focused.
  • Persistent State: Maintain agent plans, learned preferences, and intermediate results across long-running tasks or multiple sessions.
  • Dynamic Context Loading: Load only relevant information on demand, improving efficiency and reducing token waste.
  • Sub-Agent Communication: Facilitate robust communication between agents by sharing state through a common filesystem workspace.
  • Use Case: An agent processing a large codebase can offload detailed code analysis results to files, then use grep to retrieve specific function definitions only when needed, rather than keeping the entire analysis in its active context.

Quick Start

Use the filesystem-context skill to save large tool outputs to files instead of keeping them in the context window.

Frequently Asked Questions about filesystem-context

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

FAQPage Schema
How do I manage agent context window bloat when processing large tool outputs?

Manage agent context window bloat by offloading large tool outputs to the filesystem, keeping the active context clean and loading data on demand. This prevents token waste and maintains processing efficiency.

Can I persist agent memory and state across multiple sessions?

Yes, you can persist agent memory and state across multiple sessions by saving plans, learned preferences, and intermediate results to files. This enables continuous state management for long-running tasks.

How does dynamic context loading work for complex agent tasks?

Dynamic context loading works by offloading large data to the filesystem and retrieving specific information on demand using file I/O and search utilities. This allows agents to load only relevant context when needed.

What's the best way to share state between sub-agents working on the same task?

Share state between sub-agents by using a common filesystem workspace. Agents communicate by writing and reading intermediate results from shared files, facilitating robust collaboration without context overlap.

When do I need file-based memory for agent context management?

You need file-based memory when working with large codebases, massive logs, or long-running tasks that exceed fixed context windows. It enables scratch pads, plan persistence, and dynamic skill loading.

Does filesystem context management support dynamic skill loading?

Yes, filesystem context management supports dynamic skill loading through file I/O operations. Agents can load specific skills and relevant information on demand from the filesystem, reducing token waste.