ctx-remind

Manage session reminders. Use when the user says 'remind me to...' or asks about pending reminders.

41 stars

Best use case

ctx-remind is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Manage session reminders. Use when the user says 'remind me to...' or asks about pending reminders.

Teams using ctx-remind should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/ctx-remind/SKILL.md --create-dirs "https://raw.githubusercontent.com/ActiveMemory/ctx/main/internal/assets/claude/skills/ctx-remind/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/ctx-remind/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How ctx-remind Compares

Feature / Agentctx-remindStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Manage session reminders. Use when the user says 'remind me to...' or asks about pending reminders.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

Manage session-scoped reminders via `ctx remind` commands using
natural language. Translate what the user says into the right
command.

## When to Use

- User says "remind me to..." or "remind me about..."
- User asks "what reminders do I have?"
- User wants to dismiss or clear reminders
- User mentions reminders surfaced at session start

## When NOT to Use

- For structured tasks with status tracking (use `ctx add task`)
- For sensitive values or quick notes (use `ctx pad`)
- For architectural decisions (use `ctx add decision`)
- Create a reminder only when the user explicitly says "remind me":
  for everything else, let the conversation proceed without creating records

## Command Mapping

| User intent                          | Command                                       |
|--------------------------------------|-----------------------------------------------|
| "remind me to refactor swagger"      | `ctx remind "refactor swagger"`               |
| "remind me tomorrow to check CI"     | `ctx remind "check CI" --after YYYY-MM-DD`    |
| "remind me next week to review auth" | `ctx remind "review auth" --after YYYY-MM-DD` |
| "what reminders do I have?"          | `ctx remind list`                             |
| "dismiss reminder 3"                 | `ctx remind dismiss 3`                        |
| "clear all reminders"                | `ctx remind dismiss --all`                    |

## Execution

**Add a reminder:**
```bash
ctx remind "refactor the swagger definitions"
```

**Add with date gate:**
```bash
ctx remind "check CI after the deploy" --after 2026-02-25
```

**List reminders:**
```bash
ctx remind list
```

**Dismiss by ID:**
```bash
ctx remind dismiss 3
```

**Dismiss all:**
```bash
ctx remind dismiss --all
```

## Natural Language Date Handling

The CLI only accepts `YYYY-MM-DD` for `--after`. You must convert
natural language dates to this format.

| User says                | You run                                                 |
|--------------------------|---------------------------------------------------------|
| "remind me next session" | `ctx remind "..."` (no `--after`)                       |
| "remind me tomorrow"     | `ctx remind "..." --after YYYY-MM-DD` (tomorrow's date) |
| "remind me next week"    | `ctx remind "..." --after YYYY-MM-DD` (7 days from now) |
| "remind me about X"      | `ctx remind "X"` (no `--after`, immediate)              |
| "remind me after Friday" | `ctx remind "..." --after YYYY-MM-DD` (next Saturday)   |

If the date is ambiguous (e.g., "after the release"), ask the user
for a specific date.

## Important Notes

- Reminders fire **every session** until dismissed: no throttle
- The `--after` flag gates when a reminder starts appearing, not when
  it expires
- IDs are never reused: after dismissing ID 3, the next gets ID 4+
- Reminders are stored in `.context/reminders.json` (committed to git)
- After creating or dismissing, show the command output so the user
  can confirm the action

Related Skills

ctx-verify

41
from ActiveMemory/ctx

Verify before claiming completion. Use before saying work is done, tests pass, or builds succeed.

ctx-skill-creator

41
from ActiveMemory/ctx

Create, improve, test, and deploy skills. Full skill lifecycle from intent to working skill file.

ctx-sanitize-permissions

41
from ActiveMemory/ctx

Audit tool permissions for dangerous or overly broad entries. Use to ensure safe agent configuration.

ctx-recall

41
from ActiveMemory/ctx

Browse session history. Use when referencing past discussions or finding context from previous work.

ctx-prompt

41
from ActiveMemory/ctx

Apply, list, and manage saved prompt templates from .context/prompts/. Use when the user asks to apply, list, or create a reusable template like code-review or refactor.

ctx-journal-normalize

41
from ActiveMemory/ctx

Normalize journal source markdown for clean rendering. Use after journal site shows rendering issues: fence nesting, metadata formatting, broken lists.

ctx-import-plans

41
from ActiveMemory/ctx

Import plan files into project specs directory. Use to convert external plans into project-tracked specs.

ctx-compact

41
from ActiveMemory/ctx

Archive completed tasks and trim context. Use when context files are growing large.

ctx-check-links

41
from ActiveMemory/ctx

Audit docs for dead links. Use before releases, after restructuring docs, or when running a documentation audit.

ctx-add-task

41
from ActiveMemory/ctx

Add a task. Use when follow-up work is identified or when breaking down complex work into subtasks.

ctx-add-learning

41
from ActiveMemory/ctx

Record a learning. Use when discovering gotchas, bugs, or unexpected behavior that future sessions should know about.

ctx-add-decision

41
from ActiveMemory/ctx

Record architectural decision. Use when a trade-off is resolved or a non-obvious design choice is made that future sessions need to know.