Nudge CLI

How to use the nudge CLI — commands, flags, setup, and onboarding. Use this skill whenever the user wants to create a task, add a secret, check status, confi...

This is a how-to for a CLI that intentionally collects and can publish sensitive, personal 'secrets' to third parties — that's the product, not a hidden behavior. Before installing or using it: 1) Do not run 'curl | sh' unless you have inspected the script and trust the upstream repo; prefer vetted packages or verify checksums. 2) Review the GitHub repo (neilsanghrajka/nudge) and Homebrew tap to confirm authorship and review install scripts. 3) Be cautious supplying tokens on the command line (they can end up in shell history); prefer storing credentials securely. 4) Understand legal/privacy/ethical consequences of sending private information to contacts or services; get consent where appropriate. 5) If you want this skill only as documentation (no installs), you can use the guidance without running installers. If you need a deeper analysis (e.g., review of the remote install script or the upstream repo contents), provide the install script or repo URL and I can examine it — that would raise confidence in the assessment.

Type: OpenClaw Skill Name: nudge-cli Version: 1.1.0 The nudge-cli skill facilitates the installation and use of an 'accountability tool' that explicitly encourages users to provide highly sensitive information, including 'embarrassing secrets' and third-party messaging tokens (e.g., Beeper/WhatsApp). While these actions align with the tool's stated purpose of social accountability, the collection of such data and the automated mechanism to broadcast it to contacts represent a significant privacy and security risk. Additionally, the installation instructions in SKILL.md promote the use of a high-risk 'curl | sh' pattern from a remote GitHub repository (neilsanghrajka/nudge).