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.
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
Intelligently organizes your files and folders across your computer by understanding context, finding duplicates, suggesting better structures, and automating cleanup tasks. Reduces cognitive load and keeps your digital workspace tidy without manual effort.
Generates creative domain name ideas for your project and checks availability across multiple TLDs (.com, .io, .dev, .ai, etc.). Saves hours of brainstorming and manual checking.
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls.
Creative research ideation and exploration. Use for open-ended brainstorming sessions, exploring interdisciplinary connections, challenging assumptions, or identifying research gaps. Best for early-stage research planning when you do not have specific observations yet. For formulating testable hypotheses from data use hypothesis-generation.
Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
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.