notion-calendar_skill

Overview

This skill manages Notion calendar databases to support date-aware search, page creation, rescheduling, and safe planning workflows. It discovers database schema, enforces time-windowed queries, and verifies every write with a read-back to ensure accuracy and safety. Designed for editorial calendars, launch schedules, and dated task boards, it balances fast CLI shortcuts with robust API fallbacks.

How this skill works

On first use it guides token and workspace setup, then inspects the target database to cache title, date, status, and assignee properties. Queries convert natural language windows (like "next week" or "this quarter") into bounded ISO ranges using a declared timezone, then search that window first. For reads it prefers a local CLI when available for speed; for schema-sensitive operations and unsupported commands it calls the Notion HTTP API. All create, update, or archive actions fetch candidates first and read back the changed page to report final values and URL.

When to use it

• Treat a Notion database as a calendar: editorial plan, content calendar, or launch schedule.
• Find pages in a specific date window (day, week, quarter) with timezone awareness.
• Create dated pages from reusable templates and ensure the right date property is set.
• Reschedule items safely with explicit verification and rollback logging.
• Update status or assignee fields for items that appear in calendar views.

Best practices

• Always let the skill discover the database schema before writing to any date field.
• Provide exact date windows or confirm the timezone when requesting time-based queries.
• Approve cached property mappings before the skill writes to your database.
• Escalate ambiguous matches: supply a page URL, ID, or precise date to avoid errors.
• Rely on the CLI for fast reads; use the API for schema migrations or complex updates.

Example use cases

• Search the content calendar for all items scheduled next week and export titles and URLs.
• Create a batch of launch checklist pages using a reusable payload template with correct start/end dates.
• Reschedule a post from July 8 to July 22 after confirming the exact row and date property.
• Mark a set of campaign pages as "Published" and verify changes by reading back each page.
• Detect ambiguous title matches and prompt for the page ID before making any destructive change.