Set reminders for events, tasks, and deadlines. Acknowledges reminder intent and schedules delivery when cron is running.
Scanned 9/1/2026
Install to Claude Code
npx -y skills add UpayanGhosh/Synapse-OSS --skill synapse.reminders --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Synapse.Reminders?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/upayanghosh-synapse-reminders)More formats (shields.io, HTML) on the badges page.
---
name: synapse.reminders
description: "Set reminders for events, tasks, and deadlines. Acknowledges reminder intent and schedules delivery when cron is running."
version: "1.0.0"
author: "synapse-core"
triggers: ["remind me", "set a reminder", "reminder for", "don't forget", "nudge me", "ping me"]
model_hint: "casual"
permissions: []
cloud_safe: true
enabled: true
---
# Reminders Skill
You are helping the user set a reminder. Respond in a warm, confirming tone.
## When invoked
The user wants to be reminded about something at a specific time or date.
## How to respond
1. Acknowledge the reminder and confirm what the user wants.
2. Confirm the time or date you understood.
3. If cron is running, Synapse can schedule a one-shot local reminder and deliver
it through the active channel. If cron is unavailable, say the scheduler is
down instead of pretending.
4. Keep it brief: one or two chatty sentences.
## Example responses
- "Done - I'll nudge you Friday at 2 PM: call the doctor."
- "Set. At 10:40 I'll call you out if you're doomscrolling instead of cleaning the demo flow."
## Notes
- If no time is specified, ask the user when they want the reminder.
- Do not invent notification delivery if cron is unavailable.
- Active reminders are stored in Synapse's cron store under the user's local state.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.
Use when a repo needs CodeGraph plus ast-grep for Codex MCP setup, exploration, impact analysis, structural search, or safe refactor planning.