NervTimer

Use this skill when the user wants OpenClaw to set a reminder timer and keep reminding until explicit completion.

This skill is designed to be published via ClawHub and installed with:

CODEBLOCK0

Required behavior

1. 1. Parse user intent into structured timer data.
2. Support one_shot and recurrent schedules.
3. Extract optional reason/purpose text from user intent.
4. When due, start nagging every 5 minutes.
5. Stop nagging only when the user explicitly says done.
6. For recurring timers: done ends only the current nagging phase, not the whole recurring schedule.

Deterministic + generative split

• - Deterministic:

• - Generative (LLM):

Files in this skill

• - INLINECODE6
• INLINECODE7
• INLINECODE8
• INLINECODE9
• INLINECODE10

Workflow

Execution rule:

• - Always execute skill scripts via bash <script-path> ....
• Do not execute scripts directly via shebang path.
• If a script call fails, immediately fall back to direct cron tool calls and inform the user briefly.
• Never keep "typing" without either creating the timer or returning a concrete error.

A) Create timer

1. 1. Build a structured intent JSON from the user message (see intent schema reference).
2. Validate it:

CODEBLOCK1

1. 3. Upsert timer state:

CODEBLOCK2

1. 4. Build cron payload(s):

CODEBLOCK3

1. 5. Call cron tool with action=add for each payload.

Important defaults:

• - For reminder output use isolated runs (sessionTarget: "isolated", payload.kind: "agentTurn").
• Route delivery to current channel context unless user requests another target.

B) Scheduled execution (nagging tick)

When a cron reminder turn runs:

1. 1. Call:

CODEBLOCK4

1. 2. If should_nag=false, do not send a reminder text.
2. If should_nag=true, generate one short reminder using:

1. 4. Message must become more urgent as nag_count increases.
2. Apply tone guardrails from escalation policy.

C) User says done

If user explicitly confirms completion (for example "done", "erledigt", "hab ich gemacht"):

1. 1. Resolve active timer.
2. Mark done:

CODEBLOCK5

1. 3. For recurring timers:

D) Ambiguity rules

• - If exactly one active nagging timer exists: auto-map completion.
• If multiple active nagging timers exist: ask a short disambiguation question.

E) Fast fallback (important for reliability)

If deterministic helper scripts cannot run for any reason:

• - create/update cron jobs directly with the cron tool in the same turn
• use the same schedule and nagging semantics
• confirm the resulting timer setup to the user
• if no schedule can be parsed confidently, ask one short clarification question

Safety and tone constraints

• - Keep reminders short (1 to 2 sentences).
• No insults, threats, or manipulative guilt language.
• "More annoyed" means stylistic urgency only, not abuse.
• Never claim the task is done unless user explicitly confirms it.

Packaging note (ClawHub)

Keep this folder self-contained so it can be published directly:

CODEBLOCK6