Principle
Use progressive disclosure for agent instructions
Do not make every future task pay the context cost of every past instruction.
Before you use it
- Use when
- A reusable agent has many procedures, references and edge cases.
Keep this limit in mind
- Deferred context is useless if triggers are vague or search is weak; critical safety rules may need to remain always visible.
An idea to explore.
Try this idea.
Inspect the example, try the idea in your situation, then check your next move.
Why it matters
Keep the always-loaded layer small: purpose, trigger cues and essential constraints. Put task procedures in an invoked skill or workflow, and supporting references behind links or files that can be opened when needed. Design names and descriptions so the agent can discover the right material without preloading it all.
An example
A GitHub agent sees one short rule for release work; the detailed release checklist and rollback references load only when a release task is detected.
Check your result
Removing an unrelated skill's full text from a normal task does not reduce success.
Save and practise this idea
My learning
Read. Recall. Repeat.
Save this idea and return to it on any device.
Keep exploring
Connected ideas
You are readingUse progressive disclosure for agent instructions
From this idea
This idea is useful withTurn a recurring AI workflow into a skill only when the trigger is clear
Ideas that link here
These ideas link to this one. Check their conditions and limits before use.
Useful with this ideaRetrieve tool schemas just in time
Evidence and sources
Anthropic describes progressive disclosure as letting agents discover relevant context incrementally instead of loading all available material up front.
Progressive retrieval depends on discoverability and can be slower than up-front loading.
Effective context engineering for AI agents · Agentic search and progressive disclosure
All sources (1)
Edition and review
Version 0.1.0
No review details are supplied for this edition.