Notify with Pushover
Analysis
This skill does what it claims—sends Pushover notifications—but users should be aware it uses Pushover credentials and can send phone alerts when invoked.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Checks for instructions or behavior that redirect the agent, misuse tools, execute unexpected code, cascade across systems, exploit user trust, or continue outside the intended task.
--priority -1|0|1|2
The skill can send Pushover messages with configurable priority, including emergency priority when retry and expire values are provided. This is part of the Pushover notification use case, but it can cause repeated or urgent alerts if invoked carelessly.
For recurring alerts, prefer `cron` to schedule reminders; the cron job text can instruct Ted to run this skill.
The documentation suggests user-configured recurring alerts through cron. The skill does not install persistence itself, but users should notice that recurring notifications can continue until the cron job is removed.
Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.
const token = process.env.PUSHOVER_APP_TOKEN || process.env.PUSHOVER_TOKEN || args.token; const user = process.env.PUSHOVER_USER_KEY || process.env.PUSHOVER_USER || args.user;
The script uses Pushover account credentials to send notifications. This is required for the stated purpose, but users should recognize that it grants the skill authority to send messages through their Pushover account.