Pushary cowork

Skill Pushary/pushary-skill/skills/pushary-cowork

Phone notifications and human-in-the-loop for Claude Cowork through the Pushary connector. Use when working inside a Cowork session and the user says things like ping me on my phone when this is done, ask me before doing anything risky, keep me in the loop while I am away, or notify me if you get stuck. Sends completion alerts, asks questions (yes/no, multiple choice, or free text) via push, and gets answers from the user's lock screen. Cooperative only, Cowork has no hooks. Pushary is a hosted service, $9.99/mo after a 7-day card-first trial.From its SKILL.md

Install

npx -y skills add Pushary/pushary-skill --skill pushary-cowork

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.9 KB, 531 tokens by cl100k_base, as published. Nobody here has run it

Pushary for Claude Cowork

Pushary is connected as a custom connector. It reaches the user on their phone, where they answer from the lock screen. Use it proactively. Do not wait for the user to ask.

When to reach out

You need a decision or a clarifying answer. Call ask_user instead of guessing or stalling. Use type confirm for yes or no, select for a fixed set of options, and input for free text.
You are about to do something risky or irreversible. Deleting or overwriting files, spending money, sending anything external, bulk changes: call ask_user with type confirm first and wait for approval.
A task finishes. Call send_notification with a short summary of what changed.
You are blocked or hit an error you cannot resolve. Call send_notification so the user knows, and ask_user if you need a decision to continue.

How to wait for answers

A question stays open for 10 minutes. wait_for_answer blocks for up to about 55 seconds per call. If it returns without an answer, call wait_for_answer again with the same question id before giving up.
On long tasks where the user might be away, prefer send_notification with context.askQuestion over a blocking ask_user. The user gets a normal push and answers from the notification page whenever they pick up their phone. Poll the returned linkedCorrelationId with wait_for_answer when you need the result.
Use cancel_question to retract a question that is no longer needed.

Conventions

Pass agentName as Claude Cowork - <task name> on every call, so the user knows which session is asking and their dashboard groups the session correctly.
Keep questions short and decision-shaped. One sentence of context, then the ask. The user is reading a lock screen, not a report.
Do not ask through Pushary for things you can safely decide yourself. Reserve it for real decisions, risky steps, completions, and errors, so a ping always means something.

If the connector is missing

If no Pushary tools are available in this session, the connector is not enabled. Tell the user once: Pushary is not connected in this session. Enable it under Customize, Connectors, or set it up at https://pushary.com/docs/agents/guides/claude-desktop. Then continue the task without it.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.