context-engineering

Structure agent context with progressive disclosure and attention budgeting.

Updated Jan 20, 2026
One-click install
npx skills add https://github.com/hitsumabushi334/KGpaper --skill context-engineering-hitsumabushi334
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: context-engineering
Source: https://github.com/hitsumabushi334/KGpaper/tree/main/.agent/Skills/context-engineering
Command: npx skills add https://github.com/hitsumabushi334/KGpaper --skill context-engineering-hitsumabushi334

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Context in agent systems is often bulky, opaque, and brittle, causing degraded performance as the conversation grows. This Skill provides a principled approach to manage, load, and constrain context to sustain reliability and efficiency.

Core Features & Use Cases

  • Progressive disclosure: load only the necessary parts of context at request time, reducing token usage and latency.
  • Context budgeting and degradation awareness: design prompts and tool data to respect attention budgets and minimize quality loss.
  • Edge-positioned critical information: place essential instructions at the edges of the context window for robust recall.
  • Sub-agent isolation: partition tasks into isolated contexts to prevent cross-task contamination.
  • Multi-agent workflow guidance: apply these principles when building prompts, commands, or sub-agents in complex pipelines.

Quick Start

Start by mapping a current prompt pipeline to identify system prompts, tools, and retrieved documents. Then introduce just-in-time loading rules and edge-positioned constraints to reduce context size while preserving signal.

Frequently Asked Questions about context-engineering

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

FAQPage Schema
How do I structure context in multi-agent workflows to prevent performance degradation?

Manage context in multi-agent systems by enforcing progressive disclosure and context budgeting to load only necessary data at request time. This prevents cross-task contamination through sub-agent isolation, sustaining agent reliability while reducing token usage and latency as conversations grow.

What is context budgeting and how does it optimize prompt management?

Context budgeting optimizes prompt management by designing prompts and tool data to respect attention budgets and minimize quality loss. It reduces overall context size while preserving signal, ensuring agents process only essential information without degraded performance as conversations grow.

How can I reduce token usage and latency when loading retrieved documents into agent systems?

Reduce token usage and latency by applying progressive disclosure to load only necessary parts of retrieved documents at request time. Map current prompt pipelines to identify system prompts and tools, then introduce just-in-time loading rules to minimize context size while preserving signal.

Why does my agent forget critical instructions as the message history grows?

Agents forget critical instructions as message history grows because bulky context degrades attention and recall. Place essential instructions at the edges of the context window for robust recall, and apply context isolation to partition tasks, preventing critical information from being lost mid-context.

When should I isolate sub-agents in a multi-agent pipeline?

Isolate sub-agents in multi-agent pipelines when you need to prevent cross-task contamination and sustain reliability. Partitioning tasks into isolated contexts ensures tool outputs, message history, and retrieved documents from one task do not degrade another task's processing performance.