twhsi/fantastical-calendar
Create Fantastical calendar events and reminders from Codex on macOS. Use when the user asks Codex to add, schedule, parse, preview, or send a meeting, appointment, task, reminder, time block, daily plan item, 行事曆, 日曆, 會議, 待辦, or 提醒 into Fantastical.
npx skills add https://github.com/twhsi/skills --skill fantastical-calendar
Use this skill to turn a user's natural-language scheduling request into a Fantastical event or reminder through the local macOS Fantastical app.
Prefer the bundled script over ad hoc AppleScript:
python3 scripts/fantastical_parse.py "Project review on 2026-06-19 at 10:00" --notes "Prep deck before the call"
The script defaults to preview mode: it opens Fantastical with the parsed item but does not add it immediately.
--notes instead of overloading the event title.scripts/fantastical_parse.py from this skill folder.Use preview mode unless the user explicitly asks to add/create/schedule it now or has confirmed the parsed result.
Preview:
python3 scripts/fantastical_parse.py "Deep work on 2026-06-19 from 09:00 to 11:00"
Add immediately:
python3 scripts/fantastical_parse.py "Deep work on 2026-06-19 from 09:00 to 11:00" --add-immediately
Dry run for validation:
python3 scripts/fantastical_parse.py "Deep work on 2026-06-19 from 09:00 to 11:00" --dry-run
Use explicit, Fantastical-friendly wording:
Team sync on 2026-06-19 from 10:00 to 10:30Call Alice on 2026-06-20 at 15:00 for 45 minutesRemind me to submit expenses on 2026-06-21 at 09:00Focus block on 2026-06-18 from 14:00 to 16:00For Chinese user requests, keep the user-facing reply in Chinese, but send Fantastical an explicit mixed or English sentence if it reduces parsing risk.
Read references/fantastical-macos.md only when debugging the app integration, updating the script, or adapting it to another Fantastical version.
The current script uses AppleScript parse sentence first and can fall back to the Fantastical URL scheme when needed.
Take twhsi/fantastical-calendar from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.