How do I install the Reminder Format skill?

Run npx skillmds@latest add rustam-z/reminder-format in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Reminder Format skill do?

House format for the text passed to reminder_set. Read before calling reminder_set, and again before editing a reminder (cancel + re-create). Three rules — open with the literal marker , state the goal in one line, then list numbered steps the future-self should run when the reminder fires. Keeps fired envelopes self-explanatory and actionable. It is listed under Coding & Dev Tools on SkillMD.

Is Reminder Format safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Reminder Format?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Reminder Format free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.

Who published Reminder Format?

Rustam-Z (@rustam-z) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Reminder Format by rustam-z — Agent Skill

Name: Reminder Format
Author: Rustam-Z

Reminder Format

House format for the text passed to reminder_set. Read before calling reminder_set, and again before editing a reminder (cancel + re-create). Three rules — open with the literal marker <THIS IS A REMINDER>, state the goal in one line, then list numbered steps the future-self should run when the reminder fires. Keeps fired <reminder> envelopes self-explanatory and actionable.

Rustam-Z Updated Sep 22, 2026

File contents

Skill: reminder-format

Reference skill (no <reminder> envelope required). Read it before calling reminder_set — and again before editing a reminder (which means reminder_cancel + a fresh reminder_set). The format applies to the text argument; cron and trigger_at are unaffected.

The reminder text is a self-prompt: when the timer fires, this exact string lands in your input as <reminder>…</reminder> and re-orients a fresh turn. Past-you is briefing future-you. Write it that way.

The three rules

Opening line. The first line of text is exactly <THIS IS A REMINDER> — literal, including the angle brackets and uppercase. It anchors future-you immediately, before any envelope parsing.
Goal line. One short sentence right after the opener, prefixed Goal:. State why this reminder exists — the outcome past-you wanted.
Steps. A numbered list (1., 2., …) of the concrete actions future-you should take when it fires. One line per step, imperative voice ("send X", "check Y", "DM the owner if Z"). No nesting, no sub-bullets.

Example

<THIS IS A REMINDER>
Goal: follow up with Alice on the GitLab MR she opened yesterday.
1. Read the MR status via WebFetch.
2. If still open, DM Alice asking if she needs review help.
3. If merged, send a thumbs-up reaction in the original chat.

Don'ts

No markdown headers, no prose paragraphs in place of steps.
Don't skip the opener even for one-liners — the literal marker is the cue.

---name: reminder-formatdescription: House format for the text passed to reminder_set. Read before calling reminder_set, and again before editing a reminder (cancel + re-create). Three rules — open with the literal marker <THIS IS A REMINDER>, state the goal in one line, then list numbered steps the future-self should run when the reminder fires. Keeps fired <reminder> envelopes self-explanatory and actionable.license: MIT---# Skill: reminder-formatReference skill (no `<reminder>` envelope required). Read it beforecalling `reminder_set` — and again before editing a reminder (whichmeans `reminder_cancel` + a fresh `reminder_set`). The format appliesto the `text` argument; cron and `trigger_at` are unaffected.The reminder text is a self-prompt: when the timer fires, this exactstring lands in your input as `<reminder>…</reminder>` and re-orientsa fresh turn. Past-you is briefing future-you. Write it that way.## The three rules1. **Opening line.** The first line of `text` is exactly `<THIS IS A REMINDER>` — literal, including the angle brackets and uppercase. It anchors future-you immediately, before any envelope parsing.2. **Goal line.** One short sentence right after the opener, prefixed `Goal:`. State *why* this reminder exists — the outcome past-you wanted.3. **Steps.** A numbered list (`1.`, `2.`, …) of the concrete actions future-you should take when it fires. One line per step, imperative voice ("send X", "check Y", "DM the owner if Z"). No nesting, no sub-bullets.## Example```<THIS IS A REMINDER>Goal: follow up with Alice on the GitLab MR she opened yesterday.1. Read the MR status via WebFetch.2. If still open, DM Alice asking if she needs review help.3. If merged, send a thumbs-up reaction in the original chat.```## Don'ts- No markdown headers, no prose paragraphs in place of steps.- Don't skip the opener even for one-liners — the literal marker is the cue.

Frequently asked questions