Palest Ink - Activity Tracker

Track and recall your daily activities including git commits, web browsing, shell commands, and VS Code edits. Use this skill whenever the user asks about th...

This skill is coherent with an activity-tracking purpose, but it is invasive and persistent. Before installing: (1) Review collectors/install.sh and collectors/uninstall.sh to see exactly what files/plists and git hooks will be written and how to remove them. (2) Inspect any launchd plist the installer creates and confirm it runs only as your user (not root) and what command it runs. (3) Review the git_hook.sh content to ensure hooks don’t leak data or run unwanted commands. (4) Be aware the collectors read browser history DBs, shell histories, and repo contents and will fetch page content for visited URLs (collect_content.py uses urlopen). Although the package claims data stays local, these operations access sensitive data—consider installing only on a throwaway account/VM or after auditing the scripts. (5) Confirm the uninstall path works and that config/data are stored under ~/.palest-ink and not elsewhere. (6) If you’re uncomfortable with continuous monitoring or granting Full Disk Access/Accessibility, do not install. If you need help, ask for a line-by-line review of install.sh, the launchd plist, and the git hook scripts before running them.

Type: OpenClaw Skill Name: palest-ink Version: 0.1.0 The OpenClaw skill 'palest-ink' is classified as suspicious due to its extensive data collection, high system privileges, and persistent execution mechanisms, even though its stated purpose is benign activity tracking. Key indicators include: 1) The `install.sh` script sets up a `launchd` agent to run every 15 seconds and configures global Git hooks (`core.hooksPath`), granting significant system-wide persistence and control. 2) The skill explicitly requests 'Full Disk Access' and 'Accessibility' permissions, enabling it to collect highly sensitive data such as web browsing history (including page content), shell commands, VS Code edits, and app focus. 3) The `collect_content.py` script performs outbound network requests to fetch content from arbitrary URLs found in the user's browsing history, a risky capability that could be exploited if the URLs themselves are malicious. While the code does not show explicit malicious intent (e.g., exfiltration to unauthorized endpoints), the broad scope of data collection and the powerful system modifications warrant a 'suspicious' classification.