Skill

event-to-task

Migrate a Google Calendar event into a Todoist task — two-part: create the task, then delete the event. For things miscaptured as appointments.

npx claudepluginhub danielrosehill/claude-code-plugins --plugin schedule-manager

Tool Access

This skill uses the workspace's default tool permissions.

Preview

1. **Read config.** Workspace MCP, Todoist MCP.

SKILL.md

Similar Skills

using-superpowers

180.9k

Mandates invoking relevant skills via tools before any response in coding sessions. Covers access, priorities, and adaptations for Claude Code, Copilot CLI, Gemini CLI.

3 files

superpowers

Stats

Stars0

Forks0

Last CommitApr 28, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Event → Task Migration

Steps

Read config. Workspace MCP, Todoist MCP.

Identify the event(s). Accept ID, URL, or fuzzy reference.

Gather missing task fields. An event likely lacks: priority, project, labels. The event's title becomes the task content; description carries over to task notes; start date becomes the task due (unless user wants no date).

Create tasks first (delegate to create-task or batch-create-tasks).

Verify creation succeeded. Capture new task IDs.

Delete events only after confirmation. Warn if the event has attendees — deletion sends cancellation notices. If attendees exist, ask whether to delete (sending notices) or just remove the user from the invite.

Report per-row: new task link + event deletion status.

Notes

Two-part operation; never delete before the task exists.

Be especially careful with events that have attendees — cancellations are visible and irreversible.

Event → Task Migration

Steps

Read config. Workspace MCP, Todoist MCP.
Identify the event(s). Accept ID, URL, or fuzzy reference.
Gather missing task fields. An event likely lacks: priority, project, labels. The event's title becomes the task content; description carries over to task notes; start date becomes the task due (unless user wants no date).
Confirm the migration plan as a table: | Event | → Task content | Due | Project | Priority |
Create tasks first (delegate to create-task or batch-create-tasks).
Verify creation succeeded. Capture new task IDs.
Delete events only after confirmation. Warn if the event has attendees — deletion sends cancellation notices. If attendees exist, ask whether to delete (sending notices) or just remove the user from the invite.
Report per-row: new task link + event deletion status.

Notes

Two-part operation; never delete before the task exists.
Be especially careful with events that have attendees — cancellations are visible and irreversible.