← ClaudeAtlas

reminderslisted

Review and manage every Cuebird decision — active phone reminders, past ones, declined and deferred offers. Use when the user asks what reminders exist, wants to change/cancel/re-enable one, revisit a "no", or clean up history.
itsmynamee/cuebird · ★ 0 · Code & Development · score 72
Install: claude install-skill itsmynamee/cuebird
# Cuebird: reminders (the journal) The journal records every decision ever made about a reminder — accepted, declined, deferred, done, cancelled. The Reminders app owns notification content; the journal owns history. Nothing here is final: every past "no" can become a "yes". Below, `$CUEBIRD` denotes the resolved absolute path to the CLI — it is notation, not a shell variable: each bash command you run is its own fresh shell, so substitute the literal path directly into every command below (or, if you do assign a shell variable, only rely on it within one single bash invocation, never across separate tool calls). Resolve `$CUEBIRD` using these methods, in order — never guess beyond them: 1. If your skill invocation provides a "Base directory for this skill" (or equivalent), use it directly: `CUEBIRD=<that-base>/../../scripts/cuebird.sh` 2. Otherwise, if the environment variable `CLAUDE_PLUGIN_ROOT` is set in your Bash environment, use `"$CLAUDE_PLUGIN_ROOT/scripts/cuebird.sh"`. 3. Only if both of the above fail, locate the installed plugin under `~/.claude/plugins`: `ls -d ~/.claude/plugins/*/cuebird*/scripts/cuebird.sh 2>/dev/null | head -1` ### Shell safety (read before running any command below) Every value you interpolate into these commands — id, title, due date, status, project name — is either free text or came from journal content you don't fully control. Double-quoted shell strings still expand backticks, `$(...)`, and `$VAR` inside them, so free t