Notification & Reminder Hub

Plan a reminder register that connects each alert to a trigger, owner and channel. The skill prioritizes the few reminders that change behavior. It builds empty rule and notification templates on request.

The skill separates advice, review, conversion and build requests before producing artifacts. Advice receives a short recommendation and an offer of a relevant build. An explicit build request proceeds once essential missing facts are resolved. It asks one question at a time, reuses answers already supplied and stops when further answers would not change the deliverable. Unknown information remains unknown rather than receiving invented values.

Use it for a reminder hub, notification tracker, automated-alerts log or task reminder plan. Establish frequency, delivery channels, quiet hours, triggering data, ownership and opt-outs.

It does not send messages itself or connect to a messaging platform. Remove reminders nobody acts on; the workflow is a specification for an integration rather than an active delivery system. The skill does not calculate payroll, tax, leave balances or KPIs. Automation, reminders and synchronization require an integration layer. Legal, tax and HR review is required before templates drive real decisions.

The planned workflow is trigger, rule check, message sent, acknowledgement and escalation if ignored. Inputs establish whether the deliverable is a reminder list, rule set or both, and how current reminders are managed. Its 12 fields are Notification Title, Department, Message, Notification ID, Priority, Recipient, Related Record, Scheduled Date, Sent Date, Status, Trigger Module and Type. Related Record is the relation field. Priority ranges from Low to Urgent; statuses include Scheduled, Sent, Delivered, Failed and Cancelled. Type options are Email, WhatsApp, Slack, Calendar and Task; they label delivery channels without creating connections to those services.

Requested artifacts can include CSV, SQL DDL, JSON Schema, Notion property mappings or an Excel workbook. The formats derive from one field list: CSV and JSON retain matching display names, while SQL uses normalized identifiers. Dates retain date types, money retains currency types and cross-table references retain relation types. Select options are a starting set that can be renamed to match the business.

One SQL example is:

CREATE INDEX idx_notification_reminder_hub_status ON notification_reminder_hub (status);

Templates are empty by default. Example rows are produced only on request and remain obviously synthetic. Sensitive identifiers should not be repeated unnecessarily during a requested review. Machine-readable data stays separate from explanatory prose and any material validation failures. Excel-compatible CSV uses UTF-8 with a byte order mark and accompanying guidance about number, date and currency columns. An XLSX workbook is a separate requested output rather than a renamed CSV.

The Notion output routes to notion-manual-import for CSV, property mappings, import steps and verification. Manual mappings require no connection. Requested live workspace changes require actual tool access, a verified target and authorization. Imported columns may initially be Text and need their mapped property types applied. Relation links resolve after both relevant databases are imported. A static mapping alone does not establish a completed workspace change.