← ClaudeAtlas

pushary-human-in-the-looplisted

Design and build a human-in-the-loop (HITL) approval step into an AI agent or an agent product. Use this skill when you are writing or changing agent code and need to decide which actions should ask a human first, who answers, which question type to use, how long to wait and what happens when nobody answers, or when you are adding approval to LangGraph, the Vercel AI SDK, the OpenAI Agents SDK, Mastra, CrewAI, Pydantic AI, an MCP client or a REST backend. Explains what framework pauses such as LangGraph interrupt() do and do not do, and how to ask a human for approval by push notification on their phone with Pushary and get the answer back. Use it for requests such as add an approval step to my agent, require human sign-off before this tool runs, add human review to my LangGraph graph, or let my users approve what my agent does. For an agent that already has the Pushary tools and needs to ask its own user now, use the pushary skill instead.
Pushary/pushary-skill · ★ 1 · AI & Automation · score 70
Install: claude install-skill Pushary/pushary-skill
# Human-in-the-loop for AI agents A human-in-the-loop step stops an AI agent before a consequential action, asks a person, and continues only on their answer. This skill covers when to add one, the choices that shape it, and how to build it with Pushary in each way people build agents. If your agent already has the Pushary MCP tools and needs the rules for calling them, use the `pushary` skill. It also covers setting Pushary up for a person. ## When to ask a person Ask before the agent: - **Does something it cannot undo.** Deleting data, dropping a table, force-pushing, overwriting a file it did not create. - **Spends money.** A payment, a refund, paid API calls at volume, provisioning anything billable. - **Speaks for someone.** An email, message or post to a customer or anyone outside the team. - **Changes production.** A deploy, a release, a publish, a migration. - **Makes a call outside its authority.** Pricing, a product decision, a security or legal tradeoff. - **Would guess on a long unattended run.** Two readings of the task are both reasonable, and the wrong one wastes the run. Do not ask when a file, a command or a lookup can settle it. That is a fact, not a decision. Do not ask when the step is reversible, costs nothing, sends nothing out and stays inside the task. Take the default and report it at the end. Do not ask twice about a step the person already approved. ## Design the step **Who answers.** Name one answerer for each kind of step: you, the develop