Schedule recurring Google Calendar events with attendees and recurrence rules.
Works with
Requires the gws-calendar skill and gws bin to be loaded
Supports full iCalendar recurrence rules (RRULE) for flexible scheduling patterns like weekly, monthly, or custom intervals
Includes attendee management, timezone configuration, and event verification via agenda view
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionrecipe-schedule-recurring-eventExecute the skills CLI command in your project's root directory to begin installation:
Fetches recipe-schedule-recurring-event from googleworkspace/cli and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate recipe-schedule-recurring-event. Access via /recipe-schedule-recurring-event in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
23.9K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
23.9K
stars
1d:["$","div",null,{"className":"prose prose-invert max-w-none prose-headings:font-semibold prose-headings:tracking-tight prose-h1:text-4xl prose-h1:mb-2 prose-h2:text-2xl prose-h2:mb-2 prose-h3:text-lg prose-h3:mb-2 prose-p:text-muted-foreground prose-li:text-muted-foreground prose-code:bg-muted prose-code:text-foreground prose-code:px-1 prose-code:py-0.5 prose-code:rounded-sm prose-code:text-sm prose-code:before:content-none prose-code:after:content-none prose-pre:bg-muted prose-pre:text-foreground prose-pre:border prose-pre:border-border prose-pre:rounded-md [&_table]:!border-[color:var(--border)] [&_th]:!border-[color:var(--border)] [&_td]:!border-[color:var(--border)]","dangerouslySetInnerHTML":{"__html":"<h1>Schedule a Recurring Meeting</h1>\n<blockquote>\n<p><strong>PREREQUISITE:</strong> Load the following skills to execute this recipe: <code>gws-calendar</code></p>\n</blockquote>\n<p>Create a recurring Google Calendar event with attendees.</p>\n<h2>Steps</h2>\n<ol>\n<li>Create recurring event: <code>gws calendar events insert --params '{"calendarId": "primary"}' --json '{"summary": "Weekly Standup", "start": {"dateTime": "2024-03-18T09:00:00", "timeZone": "America/New_York"}, "end": {"dateTime": "2024-03-18T09:30:00", "timeZone": "America/New_York"}, "recurrence": ["RRULE:FREQ=WEEKLY;BYDAY=MO"], "attendees": [{"email": "[email protected]"}]}'</code></li>\n<li>Verify it was created: <code>gws calendar +agenda --days 14 --format table</code></li>\n</ol>"}}]
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
Useful defaults in recipe-schedule-recurring-event — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
recipe-schedule-recurring-event has been reliable in day-to-day use. Documentation quality is above average for community skills.
We added recipe-schedule-recurring-event from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
recipe-schedule-recurring-event is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
recipe-schedule-recurring-event fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Keeps context tight: recipe-schedule-recurring-event is the kind of skill you can hand to a new teammate without a long onboarding doc.
We added recipe-schedule-recurring-event from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Useful defaults in recipe-schedule-recurring-event — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
I recommend recipe-schedule-recurring-event for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
recipe-schedule-recurring-event has been reliable in day-to-day use. Documentation quality is above average for community skills.
showing 1-10 of 32