← ClaudeAtlas

agent-engineeringlisted

Use when designing or evaluating a production AI agent system, choosing a multi-agent coordination pattern (orchestrator/worker, fan-out, consensus, sequential chain, evaluator/optimizer), diagnosing coordination failures (claim races, silent stalls, context contamination, runaway loops), or auditing whether an agent loop is truly production-ready. Covers the four pillars (architecture and lifecycle, task decomposition, coordination patterns, production reliability), the six reliability requirements (observability, cost budgets, idempotency, failure recovery, safety caps, claim locks), the delegation decision framework with overhead crossover, and the most common anti-patterns. Do NOT use for prompt wording (use `prompt-craft`), per-call tool efficiency (use `tool-call-strategy`), context-stack design within a single agent (use `context-engineering`), or runtime debugging of a deployed system (use `debugging`). Do NOT use for improve this prompt's wording to get better outputs.
jacob-balslev/skill-graph · ★ 0 · AI & Automation · score 68
Install: claude install-skill jacob-balslev/skill-graph
# Agent Engineering ## Coverage - The discipline's relationship to and distinction from prompt engineering, harness engineering, and traditional distributed systems - The four pillars: architecture and lifecycle management, task decomposition and context management, multi-agent coordination patterns, production reliability - The lifecycle state machine: claim → execute → verify → commit → release, with the extended research/plan/review variant for complex workflows - Context health states (ok / degraded / compact / exhausted) and their budget thresholds, plus the six observable signals of context rot - Multi-agent coordination patterns: orchestrator/worker, fan-out/merge, evaluator/optimiser, consensus/fusion, sequential chain, hybrid — and the cost/reliability trade-offs of each - The two-pass pattern (audit then fresh-context implement) for reliability-critical workflows - The eight named coordination failure modes (task stealing, context contamination, merge conflicts, silent stall, brief rot, result injection, context bloat, double-commit) with detection and mitigation - The six production reliability requirements: observability, cost budgets, idempotency, failure recovery, safety caps, claim locks — and what breaks when each is missing - The delegation decision framework: six gates with overhead crossover analysis (≈1000-token minimum subagent overhead), batch crossover at four tasks for cheap-model fan-out - The most common anti-patterns (God Agent, prompt-as-architec