filesystem-context

Offload agent context to filesystem files for scratchpads, plans, and sub-agent workspaces.

2|Updated May 30, 2026
One-click install
npx skills add https://github.com/virahitvin8/crafty-gis --skill filesystem-context-virahitvin8
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: filesystem-context
Source: https://github.com/virahitvin8/crafty-gis/tree/main/GIT_STAR/assignment-generator/antigravity-skills-main/antigravity-skills-main/skills/filesystem-context
Command: npx skills add https://github.com/virahitvin8/crafty-gis --skill filesystem-context-virahitvin8

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? LLM context windows overflow when tool outputs, plans, and multi-agent state all compete for limited tokens, causing lost information and degraded attention. This Skill uses the filesystem as a persistent overflow layer so agents store, retrieve, and update context on demand instead of stuffing everything into the prompt. ## Core Features & Use Cases - Tool Output Offloading: Write large tool outputs to timestamped scratch files and return compact references with summaries, keeping only ~100 tokens in context. - Plan Persistence: Save structured multi-step plans to disk so agents can re-read objectives and progress after context refreshes or summarization. - Sub-Agent File Workspaces: Route sub-agent findings through per-agent directories instead of lossy message chains, with dynamic skill loading and terminal log persistence. - Use Case: A research agent receives an 8000-token web search result; it writes the output to scratch/search_results_001.txt, returns a one-line summary, and greps the file later for specific details. ## Quick Start Use the filesystem-context skill to offload large tool outputs to scratch files and persist my current plan to disk.

Frequently Asked Questions about filesystem-context

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

FAQPage Schema
How do I offload large tool outputs from an LLM context window?

Write outputs exceeding roughly 2000 tokens to a timestamped scratch file and return a compact reference with a short summary. The agent later uses grep or line-range reads to retrieve only the sections it needs.

How do agents persist plans across context window refreshes?

Serialize the plan as structured JSON or YAML with step IDs and statuses, then save it to disk. The agent reloads the file at the start of each turn or after summarization to restore objective and progress awareness.

When should I use filesystem context instead of keeping everything in the prompt?

Use it when tool outputs exceed about 2000 tokens, tasks span multiple turns, or multiple agents share state. Avoid it for single-turn tasks, latency-critical paths, or when content already fits comfortably in the window.

How do sub-agents share findings without message passing?

Each sub-agent writes to its own isolated workspace directory containing findings and status files. The coordinator reads those files directly, preserving full fidelity and avoiding summarization loss across message hops.

What are the risks of scratch pad files in agent systems?

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