Skill

task-to-event

Migrate a Todoist task into a Google Calendar event — two-part: create the event, then delete the task. Useful when something captured as a task should actually be on the calendar.

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, contacts 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.

Task → Event Migration

Steps

Read config. Workspace MCP, Todoist MCP, contacts MCP.

Identify the task(s). Accept one or many Todoist tasks (ID, URL, or fuzzy reference).

Gather missing event fields. A task likely lacks: start time, duration, attendees, location. Ask the user for each missing field per task, or accept defaults (e.g., 30 min, no attendees).

Create events first (delegate to create-event or batch-create-events).

Verify creation succeeded. Capture the new event IDs.

Delete the source tasks only after every corresponding event is confirmed created. If any event creation failed, leave its task in place and report.

Report per-row: new event link + "task deleted" or "event failed, task preserved".

Notes

This is a two-part operation; never delete before the event exists. A failure mid-way must leave the user with no data lost.

Confirm explicitly before deleting tasks — the user may want to keep them for tracking.

Task → Event Migration

Steps

Read config. Workspace MCP, Todoist MCP, contacts MCP.
Identify the task(s). Accept one or many Todoist tasks (ID, URL, or fuzzy reference).
Gather missing event fields. A task likely lacks: start time, duration, attendees, location. Ask the user for each missing field per task, or accept defaults (e.g., 30 min, no attendees).
Confirm the migration plan as a table: | Task | → Event title | When | Attendees |
Create events first (delegate to create-event or batch-create-events).
Verify creation succeeded. Capture the new event IDs.
Delete the source tasks only after every corresponding event is confirmed created. If any event creation failed, leave its task in place and report.
Report per-row: new event link + "task deleted" or "event failed, task preserved".

Notes

This is a two-part operation; never delete before the event exists. A failure mid-way must leave the user with no data lost.
Confirm explicitly before deleting tasks — the user may want to keep them for tracking.