Life Control
PassAudited by ClawScan on May 10, 2026.
Overview
The skill is coherent for personal life-tracking automation, but users should review the external scripts, Telegram tokens, sensitive logs, and cron jobs before using it.
Before installing, review the referenced repo scripts and cron template, use dedicated Telegram bot tokens, verify where the Life Control database stores private data, and make sure you know how to stop scheduled routines.
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.
Running the referenced scripts could do more than the SKILL.md describes if those external files are not reviewed first.
The skill depends on external helper scripts and routines, but the supplied manifest contains only SKILL.md. This is not suspicious by itself, but the runnable behavior is outside the provided review context.
Run `skills/life-control/scripts/bootstrap.sh`... Scripts live in `routines/`... Run `telegram-sender.sh` via cron
Inspect the referenced repository scripts, routine files, and cron template before running them.
A misconfigured or exposed bot token could allow messages to be sent through the user’s Telegram bot.
Telegram credentials are expected for the stated notification feature, but they grant messaging authority for the configured bots and are not declared in the registry credential metadata.
Export Telegram chat ID + agent bot tokens.
Use only dedicated bot tokens with limited purpose, store them securely, and rotate them if exposed.
The system may accumulate private wellness, financial, relationship, and routine data that could be sensitive if shared or exposed.
The skill is intended to create persistent personal tracking data across sensitive areas of life. This is core to the purpose, but users should understand where that data is stored and reused.
track life domains (wellness, finance, fashion, career, relationships, spiritual growth) with routines
Confirm the database location, backup behavior, retention policy, and who or what agents can read the stored logs.
Cron jobs may continue running routines or sending notifications after initial setup unless removed.
The skill supports persistent scheduled automation. That is aligned with daily routines, but users should ensure it runs only at intended times and can be stopped.
Add `crontab-template.txt` entries for automatic scheduling.
Review the cron entries before installing them and document how to disable or remove the scheduled jobs.