agentleFS
jholhewresjholhewres/devclaw-skills/skills/timer/SKILL.md

timer

Skill4 starsChanged 9 months agoMITView on GitHub

Set timers, alarms, and Pomodoro sessions — runs in background

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Always run timers in background mode so the user can keep chatting.

    line 68
  2. Distinctive:

    When a timer completes, notify the user with a clear message including the original purpose.

    line 71

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Timer

You can set timers and alarms that run in the background. Use the DevClaw scheduler (cron_add) for precise time-based alerts or bash sleep for quick countdowns.

Quick timers (using sleep)

# Simple countdown — sends a message when done
sleep 300 && echo "⏰ 5-minute timer finished!"

# With a custom message
sleep 600 && echo "⏰ Time to check the oven!"

# 30 seconds
sleep 30 && echo "⏰ 30 seconds! Time's up."

Important: Use bash background:true so the timer runs in the background without blocking.

Using the scheduler (for precise times)

# Reminder at a specific time (one-shot cron)
# Format: minute hour day month weekday
cron_add --id "reminder-123" --schedule "30 14 * * *" --payload "Reminder: meeting at 3pm"

# Remove after it fires
cron_remove --id "reminder-123"

Pomodoro technique

# Work session (25 min)
sleep 1500 && echo "🍅 Pomodoro finished! Time for a 5-minute break."

# Short break (5 min)
sleep 300 && echo "🔔 Break's over! Back to work."

# Long break (15 min, after 4 pomodoros)
sleep 900 && echo "☕ Long break over! Ready for another cycle?"

Time conversion reference

InputSeconds
30s30
1m60
5m300
10m600
15m900
25m1500
30m1800
1h3600
2h7200

Tips

  • Always run timers in background mode so the user can keep chatting.
  • Convert natural language times: "5 minutes" → sleep 300, "half hour" → sleep 1800.
  • For recurring timers (e.g., "every 30 minutes"), use the scheduler with cron expressions.
  • When a timer completes, notify the user with a clear message including the original purpose.
  • For Pomodoro, track the cycle number if the user wants a full session.

Triggers

timer, set a timer, alarm, set alarm, pomodoro, countdown, temporizador, alarme, cronômetro, me avise em, lembrete em

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.