← ClaudeAtlas

pusharylisted

Push notifications and human-in-the-loop for AI agents. Use this whenever a running agent needs a human and nobody is at the terminal, such as before an irreversible or destructive action, before spending money, deploying, force-pushing or deleting, when blocked on a decision outside your authority, when running unattended and you hit a genuine ambiguity, when another skill's workflow says to confirm with the user, and when a long task finishes or fails with nobody watching. Also use it when the user says things like keep going and ping me on my phone if you need anything, notify me when my agent needs me, approve from my phone, ask me questions while I am away from the terminal, run this overnight, keep working while I am in a meeting, I am stepping away, do not wait for me, or wants a long task to run unattended. Send alerts when tasks finish or fail, ask questions (yes/no, multiple choice, or free text) via push, and get answers from the user's lock screen. Use these tools proactively - do not wait for the
Pushary/pushary-skill · ★ 1 · AI & Automation · score 70
Install: claude install-skill Pushary/pushary-skill
# Pushary - Push Notifications for AI Agents When the user says "keep going, ping me on my phone if you need anything", this is the skill that does the pinging. Pushary is an MCP server that reaches the user on their phone while they are away from the terminal: 1. **Send push notifications** to the user's phone or desktop when a task finishes or an error occurs. 2. **Ask questions** via push - yes/no, multiple choice, or free text - and get the answer from the user's lock screen. 3. **Send rich context notifications** with file changes, error details, next steps, and embedded questions. Use these tools proactively. Do not wait for the user to ask for notifications. Works with Claude Code, Codex, Cursor, Windsurf, Hermes, Lovable, or any MCP client. No Claude Max subscription required. ## Reach for This Without Being Asked Nobody has to say "ping me". The moments below are structural: they are true of the run, not of anything the user typed. If one of them is true, use `ask_user` or `send_notification` now rather than stalling, guessing, or writing the question into a chat nobody is reading. - **You are about to do something irreversible.** Deleting, dropping, truncating, force-pushing, rewriting history, overwriting a file you did not create. - **You are about to spend money or touch production.** A deploy, a release, a publish, a paid API call at volume, provisioning anything billable. - **The decision is outside your authority.** A product call, a naming call, a sche