agent-belt

Identify Folio books with low on-hand stock so the operator can replenish before the title goes out of stock. Use whenever the user asks about books running low, low stock, restock list, what's almost gone, stock audit, or which titles need reordering.

Customer support and order operations for the Folio bookstore. Use whenever the user asks about a book, an order, a refund, a return, store credit, or anything else customer-facing. All canonical data lives behind the `folio` MCP server - never invent prices, stock counts, customer details, or order history.

Identify and surface every order currently in the `processing` state, so the operator can chase down stalled fulfilment. Use whenever the user asks about stalled orders, processing backlog, things stuck in processing, or orders that haven't shipped yet.

Look up customer orders through the orders_db MCP server. Use whenever the user asks about an order, a tracking number, a delivery, or a customer's purchase history.

Operate the belt CLI to evaluate headless coding agents (Claude Code, Cursor, Codex, Gemini, and others) end to end. Use when the user asks to write or run eval scenarios, compare agents, score outputs with rules or LLM judges, register a new agent adapter, interpret reports or benchmark cards, or set up evals in CI. Also use when the user mentions agent-belt, scenario JSON, BELT_ env vars, llm_scorer_instruction, llm_scorer_evidence_files, TurnExpectation, or benchmark cards.