Calendar to Workflow

Automate meeting preparation, standup generation, and workflow creation from calendar data.

Overview

This skill transforms calendar events and scheduling data into actionable Claude Code workflows. Rather than manually reviewing your calendar and preparing for each meeting, this skill reads calendar exports (ICS files, JSON feeds, or pasted event details) and produces structured outputs: meeting briefings with participant context, standup notes summarizing yesterday's activity, and repeatable workflow scripts that integrate calendar triggers with development tasks.

The skill bridges the gap between time management and development workflows. It understands meeting types (standup, sprint planning, 1:1, design review) and tailors its output accordingly, pulling in relevant repository activity, recent commits, and open PRs to provide full context for each event.

Instructions

1. Provide calendar data in one of these formats:

• Paste raw ICS/iCal content directly into the conversation
• Point to an .ics file on disk: "read my calendar export at ~/calendar.ics"
• Describe events manually: "I have a standup at 9am, sprint planning at 10am, and a 1:1 with Sarah at 2pm"

1. Specify the desired output by telling Claude what you need:

• "Prep for today's meetings" -- generates a briefing document for each event
• "Create standup notes from yesterday" -- summarizes git activity and calendar events
• "Build a weekly workflow" -- creates a repeatable workflow script

1. Add context to improve the output:

• Mention the repository or project: "for the payments-api repo"
• Specify participants: "Sarah is the engineering manager"
• Note priorities: "focus on the deployment blockers"

1. Review and refine the generated output. The skill produces Markdown documents or shell scripts that you can edit, commit, or execute directly.

Output

The skill produces one or more of the following depending on the request:

• Meeting Briefing Document (Markdown): For each meeting, includes the event title, time, participants, agenda items inferred from context, relevant recent commits or PRs, and suggested talking points.
• Standup Notes (Markdown): A formatted summary covering what was done yesterday (from git log and calendar), what is planned today (from upcoming events), and any blockers identified from open issues or failing CI.
• Workflow Script (Bash/Markdown): A repeatable workflow that can be triggered on a schedule, combining calendar checks with development tasks like running tests, updating dashboards, or posting summaries to Slack.

Examples

E