Remove Analytics

Safely remove Google Analytics from a project. Cleans up all tracking code, dependencies, and environment variables.

This skill appears to do what it says — find and remove Google Analytics traces — but it performs destructive, pattern-based edits to your repository. Before installing or running it: 1) ensure you have a current VCS commit or backup; run the skill in a feature branch or a clone; 2) require and verify the explicit confirmation prompt before applying changes; 3) review every proposed removal (files, import deletions, package uninstall commands) to avoid removing unrelated code that matches broad patterns like 'GA_' or 'gtag'; 4) remember .env.example is edited but .env (with real values) may need manual review — the skill notes this as a manual step; 5) after changes, run tests and inspect package-lock or yarn.lock for unintended dependency changes; 6) check for server-side analytics endpoints, consent handling, or other telemetry sources that pattern searches might miss. If you want extra safety, ask the skill to produce a dry-run report (list of matches and proposed edits) and create a PR rather than applying changes directly.

Type: OpenClaw Skill Name: remove-analytics Version: 0.1.0 The skill is designed to remove Google Analytics from a project, which inherently requires file system modification (read, write, delete) and command execution (e.g., `npm uninstall`). While these are high-risk capabilities, the `SKILL.md` instructions are transparent, explicitly require user confirmation before proceeding, and consistently align with the stated purpose. The `disable-model-invocation: true` flag further mitigates prompt injection risks by preventing the agent from invoking its own model for arbitrary actions. There is no evidence of intentional malicious behavior such as data exfiltration, unauthorized access, or obfuscation.