Nudge CLI

Nudge is a command-line accountability tool with real consequences. This skill covers how to install and operate it.

For the full command reference with all flags, see references/cli-reference.md.

Installation

Homebrew (macOS and Linux)

CODEBLOCK0

Shell script (macOS and Linux)

CODEBLOCK1

Go install (requires Go toolchain)

CODEBLOCK2

Verify

CODEBLOCK3

Quick Command Reference

CODEBLOCK4

All commands support --json for machine-readable output.

Onboarding — First-Time Setup

1. Welcome

"I'm your accountability coach. I help you set deadlines with real consequences — if you don't finish on time, I'll reveal one of your embarrassing secrets to the people you care about."

2. Configure a punishment action (optional)

Check what's available: INLINECODE2

If nothing is configured, the fallback is desktop notifications. That's fine for starting out, but the real power comes from social consequences.

For WhatsApp via Beeper:
CODEBLOCK5

Verify: INLINECODE3

If they don't want to set up Beeper now, that's fine. Move on.

3. Seed the secrets bank

Ask the user to share 3-5 embarrassing secrets. This is the fun part.

"What's something you'd be mortified if your friends found out? Don't worry, I'll only reveal it if you fail."

Prompt ideas:

• - "What's the most embarrassing thing you've done recently?"
• "What's a guilty pleasure you'd never admit to?"
• "What's something weird you do when nobody's watching?"

For each:
CODEBLOCK6

Aim for a mix of severities.

4. (Optional) Add custom motivational quotes

"Is there a quote or saying that personally motivates you?"

CODEBLOCK7

5. First task

"Ready to try it? What's something you need to get done right now?"

Guide them through:

1. 1. What's the task?
2. How long do you need?
3. Why does this matter to you?
4. Which secret should be on the line?

Then create it: INLINECODE4

6. Explain the rules

• - Reminders come as the deadline approaches
• When time's up, if there's no proof of completion, the punishment fires automatically
• No reducing the punishment or cancelling without a real reason
• Partial credit doesn't exist — it's done or it's not
• Real proof required: a screenshot, a link, a diff — not just "I'm done"
• Always use --proof when completing to describe how it was verified (e.g., Strava data, PR link, screenshot)
• Always use --reason when failing to describe how failure was verified

Re-engagement

If a user hasn't created a task in a while:

• - Check history: INLINECODE7
• Reference their track record
• "It's been a while since your last nudge. Got something you've been putting off?"