check charger availbility
PassAudited by ClawScan on May 1, 2026.
Overview
The skill is generally purpose-aligned for EV charger checks, but users should verify the missing charger CLI/provenance and understand the API key plus optional notification data flow.
This skill looks benign for its stated purpose. Before installing, verify the missing `charger` CLI source, use a restricted Google Places API key, and only enable cron/Telegram notifications if you are comfortable with charger availability and address details being sent through that channel.
Findings (4)
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.
The reviewed artifacts do not show malicious behavior, but the main charger-checking executable is not available to inspect here.
The supplied manifest only includes `SKILL.md` and `scripts/charger-notify.sh`, while the documented core CLI is absent. The helper depends on a `charger` command being available, so users should verify what executable they install or place on PATH.
This skill includes a `bin/charger` CLI (Node.js) for checking charger availability.
Before using or scheduling the skill, confirm the source and contents of the `charger` CLI you install or symlink.
The skill may use a Google Places API key to make provider requests for charger data.
A Google Places API key is expected for this integration and is purpose-aligned, but the registry metadata lists no required env vars, so users should be aware of the credential requirement and possible API quota/billing exposure.
`GOOGLE_PLACES_API_KEY` (recommended in `~/.clawdbot/.env`)
Use a restricted Google Places API key with appropriate quotas, and store it only where you intend Clawdbot to access it.
If enabled, notifications may send charger availability and address details through Gateway/Telegram.
The optional Gateway cron/Telegram workflow is disclosed and user-directed, but notification output can include charger names and addresses, which may reveal location preferences.
Cron is the scheduler. It runs the helper script on a timer and sends you whatever the script prints.
Only enable scheduled Telegram notifications for targets and addresses you are comfortable sending through that notification channel.
The helper leaves a small state file in the user cache directory and may be run repeatedly if scheduled.
The helper maintains local state so it only notifies when availability changes. This is disclosed and scoped, but it is still persistent behavior users should recognize.
cache_dir="${HOME}/.cache/charger-notify"
mkdir -p "$cache_dir"
...
echo "$current" > "$state_file"Remove the Gateway cron entry and `~/.cache/charger-notify` state files if you no longer want recurring charger checks.