Get the FREE Ultimate OpenClaw Setup Guide →

context-engineering-collection

Scanned
npx machina-cli add skill Sdkwork-Cloud/skills-repository/Agent-Skills-for-Context-Engineering --openclaw
Files (1)
SKILL.md
7.6 KB

Agent Skills for Context Engineering

This collection provides structured guidance for building production-grade AI agent systems through effective context engineering.

When to Activate

Activate these skills when:

  • Building new agent systems from scratch
  • Optimizing existing agent performance
  • Debugging context-related failures
  • Designing multi-agent architectures
  • Creating or evaluating tools for agents
  • Implementing memory and persistence layers

Skill Map

Foundational Context Engineering

Understanding Context Fundamentals Context is not just prompt text—it is the complete state available to the language model at inference time, including system instructions, tool definitions, retrieved documents, message history, and tool outputs. Effective context engineering means understanding what information truly matters for the task at hand and curating that information for maximum signal-to-noise ratio.

Recognizing Context Degradation Language models exhibit predictable degradation patterns as context grows: the "lost-in-middle" phenomenon where information in the center of context receives less attention; U-shaped attention curves that prioritize beginning and end; context poisoning when errors compound; and context distraction when irrelevant information overwhelms relevant content.

Architectural Patterns

Multi-Agent Coordination Production multi-agent systems converge on three dominant patterns: supervisor/orchestrator architectures with centralized control, peer-to-peer swarm architectures for flexible handoffs, and hierarchical structures for complex task decomposition. The critical insight is that sub-agents exist primarily to isolate context rather than to simulate organizational roles.

Memory System Design Memory architectures range from simple scratchpads to sophisticated temporal knowledge graphs. Vector RAG provides semantic retrieval but loses relationship information. Knowledge graphs preserve structure but require more engineering investment. The file-system-as-memory pattern enables just-in-time context loading without stuffing context windows.

Filesystem-Based Context The filesystem provides a single interface for storing, retrieving, and updating effectively unlimited context. Key patterns include scratch pads for tool output offloading, plan persistence for long-horizon tasks, sub-agent communication via shared files, and dynamic skill loading. Agents use ls, glob, grep, and read_file for targeted context discovery, often outperforming semantic search for structural queries.

Hosted Agent Infrastructure Background coding agents run in remote sandboxed environments rather than on local machines. Key patterns include pre-built environment images refreshed on regular cadence, warm sandbox pools for instant session starts, filesystem snapshots for session persistence, and multiplayer support for collaborative agent sessions. Critical optimizations include allowing file reads before git sync completes (blocking only writes), predictive sandbox warming when users start typing, and self-spawning agents for parallel task execution.

Tool Design Principles Tools are contracts between deterministic systems and non-deterministic agents. Effective tool design follows the consolidation principle (prefer single comprehensive tools over multiple narrow ones), returns contextual information in errors, supports response format options for token efficiency, and uses clear namespacing.

Operational Excellence

Context Compression When agent sessions exhaust memory, compression becomes mandatory. The correct optimization target is tokens-per-task, not tokens-per-request. Structured summarization with explicit sections for files, decisions, and next steps preserves more useful information than aggressive compression. Artifact trail integrity remains the weakest dimension across all compression methods.

Context Optimization Techniques include compaction (summarizing context near limits), observation masking (replacing verbose tool outputs with references), prefix caching (reusing KV blocks across requests), and strategic context partitioning (splitting work across sub-agents with isolated contexts).

Evaluation Frameworks Production agent evaluation requires multi-dimensional rubrics covering factual accuracy, completeness, tool efficiency, and process quality. Effective patterns include LLM-as-judge for scalability, human evaluation for edge cases, and end-state evaluation for agents that mutate persistent state.

Development Methodology

Project Development Effective LLM project development begins with task-model fit analysis: validating through manual prototyping that a task is well-suited for LLM processing before building automation. Production pipelines follow staged, idempotent architectures (acquire, prepare, process, parse, render) with file system state management for debugging and caching. Structured output design with explicit format specifications enables reliable parsing. Start with minimal architecture and add complexity only when proven necessary.

Core Concepts

The collection is organized around three core themes. First, context fundamentals establish what context is, how attention mechanisms work, and why context quality matters more than quantity. Second, architectural patterns cover the structures and coordination mechanisms that enable effective agent systems. Third, operational excellence addresses the ongoing work of optimizing and evaluating production systems.

Practical Guidance

Each skill can be used independently or in combination. Start with fundamentals to establish context management mental models. Branch into architectural patterns based on your system requirements. Reference operational skills when optimizing production systems.

The skills are platform-agnostic and work with Claude Code, Cursor, or any agent framework that supports custom instructions or skill-like constructs.

Integration

This collection integrates with itself—skills reference each other and build on shared concepts. The fundamentals skill provides context for all other skills. Architectural skills (multi-agent, memory, tools) can be combined for complex systems. Operational skills (optimization, evaluation) apply to any system built using the foundational and architectural skills.

References

Internal skills in this collection:

External resources on context engineering:

  • Research on attention mechanisms and context window limitations
  • Production experience from leading AI labs on agent system design
  • Framework documentation for LangGraph, AutoGen, and CrewAI

Skill Metadata

Created: 2025-12-20 Last Updated: 2025-12-25 Author: Agent Skills for Context Engineering Contributors Version: 1.2.0

Source

git clone https://github.com/Sdkwork-Cloud/skills-repository/blob/main/packages/Agent-Skills-for-Context-Engineering/SKILL.mdView on GitHub

Overview

The collection provides structured guidance for building production-grade AI agent systems through effective context engineering. It covers foundational concepts, architectural patterns, and operational practices to improve context management across single and multi-agent setups.

How This Skill Works

The skill bundles foundational concepts, architectural patterns, and memory and tool design principles into actionable guidance. It helps teams design memory systems, filesystem-based context, hosted infrastructures, and efficient tool contracts to optimize signal-to-noise in context.

When to Use It

  • Building new agent systems from scratch
  • Optimizing existing agent performance
  • Debugging context-related failures
  • Designing multi-agent architectures
  • Implementing memory and persistence layers

Quick Start

  1. Step 1: Audit your current context sources—system prompts, tool definitions, retrieved docs, history, and tool outputs.
  2. Step 2: Select an architectural pattern (supervisor vs. peer-to-peer) based on task needs and coordination requirements.
  3. Step 3: Implement a filesystem-based context layer with scratch pads and plan persistence; run a representative task to validate signal-to-noise improvements.

Best Practices

  • Clearly delineate context boundaries (system instructions, tool definitions, history, and outputs) to maximize signal.
  • Choose memory design that balances structure and retrieval (e.g., knowledge graphs vs vector stores) and consider filesystem-based context for persistence.
  • Prefer robust tool contracts: deterministic interfaces, clear error information, and support for multiple response formats.
  • Plan for context degradation by monitoring attention drop-offs and mid-context loss; implement compression strategies.
  • Use hosted agent infrastructure patterns (sandbox pools, snapshots) to enable reliable, scalable experimentation.

Example Use Cases

  • Diagnosing context degradation in a centralized supervisor/orchestrator setup.
  • Persisting long-running plans with filesystem-based context and plan persistence.
  • Using memory graphs to preserve relationships in a multi-agent task.
  • Implementing filesystem-based context to offload tool outputs and enable sub-agent communication.
  • Deploying hosted agents in sandbox pools for parallel task execution.

Frequently Asked Questions

Add this skill to your agents
Sponsor this space

Reach thousands of developers