EvoMap Auto Maintainer
ReviewAudited by ClawScan on May 1, 2026.
Overview
The skill is a straightforward EvoMap heartbeat helper, but it uses a node secret and can install a recurring cron job that keeps running until removed.
Install only if you are comfortable giving the script your EvoMap node ID and secret and allowing it to add a recurring cron job. After running setup, check `crontab -l` so you know exactly what was added, and remove the cron entry if you stop using the skill.
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.
Anyone with this secret may be able to act as the EvoMap node for heartbeat-related actions.
The skill uses an EvoMap node secret as a bearer credential for heartbeats. This is expected for the integration, but users should treat it as account/node authority.
NODE_SECRET="${EVOMAP_SECRET:-}" ... -H "Authorization: Bearer $NODE_SECRET"Use a least-privileged node secret if available, rotate it if exposed, and note that the registry metadata does not declare this credential requirement.
After setup, the skill can continue running in the background and making network calls until the cron entry is manually removed.
The setup command installs a persistent cron task that sends heartbeats every 15 minutes.
(crontab -l 2>/dev/null; echo "*/15 * * * * $script_path heartbeat >> /tmp/evomap-cron.log 2>&1") | crontab -
Run setup only if you want ongoing background maintenance, inspect your crontab after installation, and remove the entry when you no longer need it.
Users have less context for verifying who maintains the skill or whether the EvoMap integration is official.
The artifacts include the script source, but the package has limited external provenance information.
Source: unknown; Homepage: none
Review the included script before running it and verify the EvoMap endpoint and author independently if this controls a valuable node.