Context Engineering for Agents
openbooklet.com/s/context-engineering-for-agentsopenbooklet.com/s/[email protected]GET /api/v1/skills/context-engineering-for-agentsContext engineering has displaced prompt engineering as the core skill. Coined by Tobi Lütke, amplified by Karpathy and Willison: it covers everything that enters the context window across a session â system prompt, retrieved content, tool descriptions, history, memory, examples.
You are now operating as an Agentic Product Architect. This master skill encodes the canonical standard for building production-grade agentic products â distilled from Anthropic, OpenAI, Cognition, Sierra, LangChain, and leading practitioners (Husain, Shankar, Horthy, Chase, Karpathy, Khattab) as
Stateless agents lose everything on crash. Production agents run for minutes to hours, call external services, wait on humans, retry transient failures. Without durable execution, every restart loses work, every flake costs tokens, every human wait pegs a process to memory.
Evaluation is the most critical and most under-invested practice in building agentic products. Hamel Husain and Shreya Shankar have codified the discipline; following it separates teams that ship from teams that demo.
Memory is an architectural decision, not a feature. Externalizing state is hard to retrofit â make the call deliberately.
In 2026 the tool-integration question has a clear answer: **MCP by default**. The ecosystem now exceeds 10,000 active servers and 177,000 registered tools. Adoption by Anthropic, OpenAI, Google, and the broader community makes it the de facto standard.
Auto-indexed from Moai-Team-LLC/agentic-product-standard
Are you the author? Claim this skill to take ownership and manage it.
Related Skills
graceful-error-recovery
Use this skill when a tool call, command, or API request fails. Diagnose the root cause systematically before retrying or changing approach. Do not retry the same failing call without first understanding why it failed.
audience-aware-communication
Use this skill when writing any explanation, documentation, or response that will be read by someone else. Match vocabulary, depth, and format to the audience's expertise level before writing.
Refactoring Expert
Expert in systematic code refactoring, code smell detection, and structural optimization. Use PROACTIVELY when encountering duplicated code, long methods, complex conditionals, or any code quality issues. Detects code smells and applies proven refactoring techniques without changing external behavior.
Research Expert
Specialized research expert for parallel information gathering. Use for focused research tasks with clear objectives and structured output requirements.
clarify-ambiguous-requests
Use this skill when the user's request is ambiguous, under-specified, or could be interpreted in multiple ways. If proceeding with a wrong assumption would waste significant work, always ask exactly one focused clarifying question before doing anything.
structured-step-by-step-reasoning
Use this skill for any problem that involves multiple steps, tradeoffs, or non-trivial logic. Think out loud before answering to improve accuracy and transparency. Apply whenever the answer is not immediately obvious.