ClawHub

AgentPing – Phone Call Alerts

v1.0.5

Phone call alerts when your agent needs urgent attention. Voice escalation with retries, snooze, and acknowledgement tracking. Never miss a critical alert.

⭐ 3· 292·0 current·0 all-time
by@dandanwei
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
Name/description (phone call alerts, escalation) align with required items: curl and a single AGENTPING_API_KEY. The API hostname (api.agentping.me) is used by the SKILL.md and README and matches the declared homepage.
ℹ
Instruction Scope
SKILL.md instructs the agent to call the AgentPing API (via curl) and to include optional metadata (task IDs, URLs, run IDs). This is within scope but be cautious: metadata can contain sensitive information — the instructions explicitly encourage including tracking data, so agents or integrators should avoid embedding secrets or private tokens in metadata.
✓
Install Mechanism
Instruction-only skill with no install spec or remote downloads; lowest-risk pattern. It assumes curl is available (declared). No archives, custom binaries, or third-party installers are used.
✓
Credentials
Only one environment variable is required (AGENTPING_API_KEY) and it's declared as the primary credential. That is proportional to a service that authenticates requests. Recommend storing the key securely and avoiding placing it into arbitrary metadata or chat messages.
✓
Persistence & Privilege
Skill is not always-enabled and does not request persistent system privileges. It does not modify other skills' configs. README suggests adding the API key to the OpenClaw config as optional setup, which is a normal convenience but not required by the skill itself.
Assessment
This skill appears coherent for phone-call escalation: it only needs curl and a single API key. Before installing: (1) verify the AgentPing service and privacy policy at agentping.me, (2) create a dedicated API key with minimal scope and store it securely (don't paste it into chat or metadata), (3) avoid putting secrets or sensitive URLs in the 'metadata' field (it is transmitted to the external service), (4) confirm you want agents to be able to autonomously invoke alerts (agent invocation is allowed by default), and (5) test with non-critical alerts/numbers first (and configure quiet hours / escalation rules) to avoid unwanted calls.

Like a lobster shell, security has layers — review code before you run it.

latestvk97272a77mgyd18fbdbdqpz1cn83sv45

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Runtime requirements

📞 Clawdis
Binscurl
EnvAGENTPING_API_KEY
Primary envAGENTPING_API_KEY

Comments