Meeting Prep
gnekt/My-Brain-Is-Full-Crew
Prepare a comprehensive brief for an upcoming meeting. An agent skill from gnekt/My-Brain-Is-Full-Crew.
Converts calendar events and schedules into Claude Code workflows, meeting prep documents, and standup notes.
Install Calendar To Workflow
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill calendar-to-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace calendar-to-workflow --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/.curated/calendar-to-workflow .claude/skills/calendar-to-workflow && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "calendar-to-workflow" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/calendar-to-workflow into .claude/skills/calendar-to-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "calendar-to-workflow", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/calendar-to-workflowType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill calendar-to-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace calendar-to-workflow --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/.curated/calendar-to-workflow .agents/skills/calendar-to-workflow && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "calendar-to-workflow" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/calendar-to-workflow into .agents/skills/calendar-to-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "calendar-to-workflow", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill calendar-to-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace calendar-to-workflow --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/.curated/calendar-to-workflow .cursor/skills/calendar-to-workflow && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "calendar-to-workflow" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/calendar-to-workflow into .cursor/skills/calendar-to-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "calendar-to-workflow", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/jeremylongshore/tons-of-skills-marketplace.git --path skills/.curated/calendar-to-workflow--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill calendar-to-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace calendar-to-workflow --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/.curated/calendar-to-workflow .gemini/skills/calendar-to-workflow && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "calendar-to-workflow" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/calendar-to-workflow into .gemini/skills/calendar-to-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "calendar-to-workflow", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install jeremylongshore/tons-of-skills-marketplace calendar-to-workflowInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill calendar-to-workflow -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/.curated/calendar-to-workflow .github/skills/calendar-to-workflow && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "calendar-to-workflow" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/calendar-to-workflow into .github/skills/calendar-to-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "calendar-to-workflow", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill calendar-to-workflow -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace calendar-to-workflow --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/.curated/calendar-to-workflow .opencode/skills/calendar-to-workflow && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "calendar-to-workflow" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/calendar-to-workflow into .opencode/skills/calendar-to-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "calendar-to-workflow", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
calendar-to-workflow- GitHub stars
- 2.8k
- Token cost
- ~1.4k tokens
- SKILL.md length
- 699 words
- Files
- 1
- Skills in repo
- 3,342
- Repo updated
- First seen
- Licence
- MIT
At a glance
Converts calendar events and schedules into Claude Code workflows, meeting prep documents, and standup notes.
- Works in 4 steps: Provide calendar data in one of these… → Specify the desired output by telling… → Add context to improve the output → …
- The user mentions calendar events
- SKILL.md covers Overview, Instructions, Output and Examples, plus 3 more sections
- Calls gh and git
What it does
Calendar To Workflow is an agent skill from jeremylongshore/tons-of-skills-marketplace. Converts calendar events and schedules into Claude Code workflows, meeting prep documents, and standup notes. Use when the user mentions calendar events, meeting prep, standup generation, or scheduling workflows. Trigger with phrases like "prep for my meetings", "generate standup notes", "create workflow from calendar", or "summarize today's schedule".
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts. Compatibility notes: Designed for Claude Code
It sits in Productivity & Automation, covering Meeting notes and agendas and Sales call preparation. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.
When your agent uses it
- The user mentions calendar events
- Standup generation
- Scheduling workflows
- With phrases like prep for my meetings
Example prompts
- “prep for my meetings”
- “generate standup notes”
- “create workflow from calendar”
- “/calendar-to-workflow”
Requirements
- Compatibility (from SKILL.md): Designed for Claude Code
- Pre-approved tools (allowed-tools): Read, Write, Edit, Bash(git:*), Bash(gh:*), Bash(chmod:*), Glob, Grep
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Provide calendar data in one of these formats
- Specify the desired output by telling Claude what you need
- Add context to improve the output
- Review and refine the generated output. The skill produces Markdown documents or shell scripts that you can edit, commit, or execute…
What it can do on your machine
Read from SKILL.md and the folder at commit cfae287. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
ReadWriteEditBash(git:*)Bash(gh:*)Bash(chmod:*)GlobGrep
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
ghgit
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
datatracker.ietf.orgcli.github.comgit-scm.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Compatibility
Designed for Claude Code
From compatibility in the SKILL.md frontmatter.
Context cost
Calendar To Workflow loads about 1.4k tokens when it runs. Until then it costs about 94 tokens; SKILL.md has 699 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 699 words, ~1,428 tokens.
Download SKILL.mdSave it as
.claude/skills/calendar-to-workflow/SKILL.md (or your agent's skills folder).- name
- calendar-to-workflow
- description
- Converts calendar events and schedules into Claude Code workflows, meeting prep documents, and standup notes. Use when the user mentions calendar events, meeting prep, standup generation, or scheduling workflows. Trigger with phrases like "prep for my meetings", "generate standup notes", "create workflow from calendar", or "summarize today's schedule".
- allowed-tools
- Read, Write, Edit, Bash(git:*), Bash(gh:*), Bash(chmod:*), Glob, Grep
- compatibility
- Designed for Claude Code
- version
- 0.14.0
- author
- Jeremy Longshore <jeremy@intentsolutions.io>
- license
- MIT
- tags
- calendar, automation, meetings, productivity, workflow
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
Provide calendar data in one of these formats:
- Paste raw ICS/iCal content directly into the conversation
- Point to an
.icsfile 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"
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
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"
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
Example 1: Daily Meeting Prep
User: "I have a sprint planning at 10am with the backend team and a design review at 2pm. Prep briefings for both."
The skill will:
- Create a sprint planning briefing listing open sprint issues, velocity from the last sprint, and items ready for estimation.
- Create a design review briefing pulling recent UI/UX changes from git history, linking to relevant Figma or mockup files found in the repo, and summarizing outstanding design-related issues.
- Output both as a single Markdown document with clear section headers.
Show full SKILL.md (238 more words)Show less
Example 2: Standup Notes from Git Activity
User: "Generate standup notes for today based on yesterday's work."
The skill will:
- Run
git log --since="yesterday" --onelineto gather recent commits. - Check for any open PRs with
gh pr list --author @me. - Identify any failing CI checks with
gh run list --limit 5. - Format the output as: "Yesterday I... / Today I plan to... / Blockers: ..."
Example 3: Weekly Recurring Workflow
User: "Create a Monday morning workflow that preps me for the week."
The skill will generate a script that:
- Reads the week's calendar events from an ICS file.
- Summarizes each day's meetings with participant counts and estimated time commitment.
- Pulls the current sprint board status.
- Outputs a weekly overview document to
docs/weekly-prep.md.
Error Handling
- No calendar data provided: Prompts the user to paste events, point to an ICS file, or describe their schedule.
- Unrecognized format: Attempts best-effort parsing and asks the user to confirm the extracted events.
- Missing git context: Skips repository-specific sections and notes which parts were omitted.
- Permission errors: Suggests checking file permissions or GitHub CLI authentication status.
Prerequisites
- Calendar data in ICS format, JSON, or plain text event descriptions
- Git repository context for commit-aware standup generation
- GitHub CLI (
gh) authenticated for PR and CI status lookups
Resources
- iCalendar (ICS) specification — event format reference
- GitHub CLI manual —
gh pr list,gh run listcommands - Git log formatting — options for activity summaries
© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/.curated/calendar-to-workflow of jeremylongshore/tons-of-skills-marketplace.
Open the folder on GitHubat commit cfae287
Compare with similar skills
Calendar To Workflow next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Calendar To Workflow this skilljeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Meeting Prepgnekt/My-Brain-Is-Full-Crew | 3.9k | — | ~2.7k | Automated safety check: Warn | Custom licence | |
| Gws Workflow Meeting Prepgoogleworkspace/cli | 31k | — | ~300 | Automated safety check: Pass | Apache-2.0 | |
| Capture Meetingkbanc85/claudia | 296 | — | ~2.1k | Automated safety check: Pass | Custom licence | |
| Meetingsalirezarezvani/claude-skills | 28k | — | ~1.5k | Automated safety check: Pass | MIT | |
| Meeting Preptechwolf-ai/ai-first-toolkit | 132 | — | ~1k | Automated safety check: Pass | MIT |
Similar skills
Gws Workflow Meeting Prep
googleworkspace/cli
Google Workflow: Prepare for your next meeting: agenda, attendees, and linked docs.
Capture Meeting
kbanc85/claudia
Process meeting notes or transcript to extract decisions, commitments, and insights.
Meetings
alirezarezvani/claude-skills
A skill your agent uses when someone wants to decide whether a meeting is worth calling, price a meeting in dollars, build a timeboxed agenda with desired outcomes, or turn messy meeting notes into…
Meeting Prep
techwolf-ai/ai-first-toolkit
Comprehensive pre-meeting briefing that gathers all relevant context from Slack, email, Google Docs, Notion, and calendar.
Calendar Prep
borghei/Claude-Skills
Generate one-page meeting briefings from structured input (attendees, prior context, decisions needed).
More from jeremylongshore/tons-of-skills-marketplace
All 3,342 skills in this repoPerforming Security Code Review
jeremylongshore/tons-of-skills-marketplace
Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.
Adapting Transfer Learning Models
jeremylongshore/tons-of-skills-marketplace
Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.
Agent Context Loader
jeremylongshore/tons-of-skills-marketplace
Execute proactive auto-loading: automatically detects and loads agents.md files.
Aggregating Performance Metrics
jeremylongshore/tons-of-skills-marketplace
Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.
Analyzing Capacity Planning
jeremylongshore/tons-of-skills-marketplace
Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.
Analyzing Database Indexes
jeremylongshore/tons-of-skills-marketplace
Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.
Related
Categories
Questions about Calendar To Workflow
What does Calendar To Workflow do?
Converts calendar events and schedules into Claude Code workflows, meeting prep documents, and standup notes. Calendar To Workflow is an agent skill from jeremylongshore/tons-of-skills-marketplace. Converts calendar events and schedules into Claude Code workflows, meeting prep documents, and standup notes.
When should I use Calendar To Workflow?
Calendar To Workflow fits situations like: the user mentions calendar events; standup generation; scheduling workflows; with phrases like prep for my meetings.
How do I install Calendar To Workflow in Claude Code?
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill calendar-to-workflow -a claude-code`. Or copy the skill folder (skills/.curated/calendar-to-workflow in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/calendar-to-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Calendar To Workflow in Codex?
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill calendar-to-workflow -a codex`. Or copy the skill folder (skills/.curated/calendar-to-workflow in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/calendar-to-workflow in your project. Codex loads it when a task matches its description.
Can I use Calendar To Workflow in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill calendar-to-workflow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/calendar-to-workflow, .gemini/skills/calendar-to-workflow, .github/skills/calendar-to-workflow and .opencode/skills/calendar-to-workflow in your project.
What does Calendar To Workflow need to run?
Going by SKILL.md and its folder, Calendar To Workflow needs the command-line tools its instructions call (gh and git). Its frontmatter pre-approves these tools: Read, Write, Edit, Bash(git:*), Bash(gh:*), Bash(chmod:*), Glob, Grep. Compatibility (from SKILL.md): Designed for Claude Code.
Does Calendar To Workflow access the network?
SKILL.md names 3 domains. As links in the text: datatracker.ietf.org, cli.github.com and git-scm.com. This is read from the text; nothing was executed.
Is Calendar To Workflow safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Calendar To Workflow use?
Calendar To Workflow is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Calendar To Workflow use?
About 1.4k tokens (SKILL.md is roughly 5.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Calendar To Workflow?
Skills that share tags, products or a category with Calendar To Workflow: Meeting Prep (gnekt/My-Brain-Is-Full-Crew, 3.9k stars), Gws Workflow Meeting Prep (googleworkspace/cli, 31k stars), Capture Meeting (kbanc85/claudia, 296 stars) and Meetings (alirezarezvani/claude-skills, 28k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Calendar To Workflow?
jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,827 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 10, 2026.
Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.