Skill

batch-create-events

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

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

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.

Batch Create Calendar Events

Steps

Read config. Workspace MCP, contacts MCP, defaults.

Accept the batch — either user provides a structured list (table, JSON, markdown) or this skill is invoked by firehose with the event subset.

Normalise rows to the same fields as create-event. Fill defaults (calendar, duration, timezone).

Resolve attendees in bulk. Deduplicate name lookups so the contacts MCP isn't called per row for repeating people. Present any ambiguous matches as a single resolution pass.

Show the full table for user confirmation. Allow row edits before write.

Create events serially via workspace MCP. If any single row fails, continue and collect failures rather than aborting the whole batch.

Report a per-row result: link if created, error if failed.

Notes

Calendar APIs throttle; a small delay between writes is fine. Prefer correctness over throughput.

Don't attempt parallel writes — the workspace MCP isn't guaranteed concurrency-safe.

Batch Create Calendar Events

Steps

Read config. Workspace MCP, contacts MCP, defaults.
Accept the batch — either user provides a structured list (table, JSON, markdown) or this skill is invoked by firehose with the event subset.
Normalise rows to the same fields as create-event. Fill defaults (calendar, duration, timezone).
Resolve attendees in bulk. Deduplicate name lookups so the contacts MCP isn't called per row for repeating people. Present any ambiguous matches as a single resolution pass.
Show the full table for user confirmation. Allow row edits before write.
Create events serially via workspace MCP. If any single row fails, continue and collect failures rather than aborting the whole batch.
Report a per-row result: link if created, error if failed.

Notes

Calendar APIs throttle; a small delay between writes is fine. Prefer correctness over throughput.
Don't attempt parallel writes — the workspace MCP isn't guaranteed concurrency-safe.