Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

task-to-event

Estrellas1

Forks0

Actualizado28 de abril de 2026 a las 11:36

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.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

danielrosehill

danielrosehill/Claude-Schedule-Manager-Plugin

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Desarrolladores de softwareOcupaciones informáticas y matemáticas·SOC 15-1252

SKILL.md

readonly

name	task-to-event
description	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.

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.

Más de este repositorio

mismo repositorio

agenda

danielrosehill/Claude-Schedule-Manager-Plugin

Manage meeting agendas as Google Docs — create, link to a calendar event description, share with attendees, or email. One skill, four sub-actions.

2026-04-281

assign-dates

danielrosehill/Claude-Schedule-Manager-Plugin

Assign due dates to Todoist tasks in batch. Walks the user through each undated task and applies their choice.

2026-04-281

assign-priorities

danielrosehill/Claude-Schedule-Manager-Plugin

Assign priorities to Todoist tasks in batch. Walks the user through each unprioritised task and applies their choice.

2026-04-281

batch-create-events

danielrosehill/Claude-Schedule-Manager-Plugin

Create multiple Google Calendar events from a structured list. Resolves attendees once across the batch, confirms the table, then writes.

2026-04-281

batch-create-tasks

danielrosehill/Claude-Schedule-Manager-Plugin

Create multiple Todoist tasks from a structured list. Confirms the table, then writes serially.

2026-04-281

create-event

danielrosehill/Claude-Schedule-Manager-Plugin

Create a single Google Calendar event. Resolves attendees via the contacts MCP. Optionally links a Drive doc (agenda) into the description.

2026-04-281

name	task-to-event
description	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.

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.