gws-calendar

Overview of gws-calendar skill

gws-calendar is the Google Calendar skill in googleworkspace/cli for managing calendars, access rules, and events through the gws CLI. It is best for people who need a reliable gws-calendar install and usage path for automation, not just a one-off prompt. The main job-to-be-done is translating calendar work into structured API calls: listing calendars, editing calendar settings, managing ACLs, and creating or updating events with less guesswork.

What gws-calendar is for

Use the gws-calendar skill when you need repeatable calendar operations in workflow automation, especially if you already use gws and want consistent API-backed behavior. It fits admins, ops users, and builders who care about permissions, calendar inventory, and event operations more than human-friendly scheduling chat.

What makes it different

The gws-calendar guide is oriented around CLI execution and API resources, not generic productivity advice. It points to helper commands like +insert and +agenda, and to concrete resources such as acl and calendarList, which makes it easier to choose the right action path before you run anything.

When it is a good fit

Choose this skill if you want the model to produce commandable calendar actions, understand the gws calendar <resource> <method> [flags] pattern, and stay inside Google Workspace conventions. It is a strong fit when the output needs to be operationally correct, auditable, and tied to the actual CLI structure.

How to Use gws-calendar skill

Install and read the right files first

For gws-calendar install, use the package manager flow in your environment and confirm the prerequisite shared skill exists: ../gws-shared/SKILL.md. The fastest first read is skills/gws-calendar/SKILL.md, then the shared skill for auth, global flags, and security rules. The repo currently shows no extra rules/, resources/, or scripts/ support files, so the main source of truth is the skill file itself.

Turn a rough goal into a usable prompt

Strong gws-calendar usage starts with the exact resource, method, scope, and constraint. For example, say: “Use gws-calendar to list all calendars I can access, then update the ACL for calendar X to give user Y reader access.” That is much better than “help me with Google Calendar,” because the skill expects a structured API task and can map it to a specific resource and method.

Follow the helper-command path

If your goal is event creation or agenda review, start with the helper commands linked in the skill: +insert for creating an event and +agenda for showing upcoming events across calendars. This is the practical gws-calendar usage path when you want speed and fewer low-level flags. For admin-style work, stay with the direct resource methods instead of forcing a helper command.

Check the resource before you ask for output

Read the resource list in SKILL.md first so you do not over-ask the model. acl is for access control rules, calendarList is for the user’s calendar list, and the skill is designed to expose additional calendar API surfaces in the same pattern. If you know the resource up front, your prompt can ask for exactly the method and flags needed, which usually produces cleaner commands and fewer back-and-forth edits.

gws-calendar skill FAQ

Is gws-calendar only for events?

No. The gws-calendar skill also covers calendar administration tasks such as ACL management and calendar list operations. If you only need a natural-language reminder or a simple scheduling sentence, a generic prompt may be enough; if you need repeatable API-style control, gws-calendar is the better fit.

Do I need to know the CLI before using it?

Not deeply. The skill is beginner-friendly for users who can follow gws calendar <resource> <method> [flags], but you should be comfortable giving structured inputs. The biggest adoption blocker is usually missing prerequisite context, especially the shared gws-shared setup and auth rules.

When should I not use this skill?

Do not use gws-calendar if your task is not really Google Calendar administration or if you cannot provide a specific resource or action. It is also a poor fit when you want a broad productivity brainstorm rather than a command-oriented workflow automation result.

Is it better than a normal prompt?

For repeated work, yes. A normal prompt may describe the intent, but the gws-calendar guide gives you a stable command shape, clearer resource boundaries, and a better chance of producing an actionable CLI sequence the first time.

How to Improve gws-calendar skill

Give the model the operational facts

The best gws-calendar results come from specifying calendar ID, principal email, intended permission level, date range, or event details up front. For example, “create a 45-minute event on the team calendar next Tuesday at 10am, title X, invite Y, no conferencing” is much stronger than “add a meeting.”

Match the method to the outcome

Common failures happen when users ask for a result instead of the API action behind it. If you need access changes, ask for acl.insert, acl.patch, or acl.update; if you need calendar inventory, ask for calendarList.list or calendarList.get; if you need scheduling output, use the helper commands or the event resource path. This keeps the gws-calendar skill aligned with the actual work.

Iterate from the first command, not from the summary

After the first output, refine based on the exact command shape, not on vague “make it better” feedback. Tighten flags, reduce assumptions, and confirm the target calendar or permission before rerunning. That iteration pattern matters most in gws-calendar for Workflow Automation, where small input changes often determine whether the command is valid, safe, and ready to execute.