agentleFS
NiazMorshed2007NiazMorshed2007/jcr/.agents/skills/gws-calendar/SKILL.md

gws-calendar

Skill19 starsChanged 58 days agoMITView on GitHub

Google Calendar: Manage calendars and events.

6 other projects use a version of this, 3 of them edited.

How people change it

All 3 edited versions we compared keep every one of its 2 rules.

Of the 3 edited versions we compared: 3 keep every rule.

We split this file and each edited version into the rules they give an agent and match them by wording. A version that adds no rule of its own and has not changed since this file last did reads as an older text, so what it lacks is not counted as dropped. We keep no past texts of a file, so that is inferred, and an edited version that started from an older text still counts its gaps as drops.

Adopted by

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projectsWeek of Oct 25: 0 new projectsWeek of Nov 1: 0 new projectsWeek of Nov 8: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Most recently taken up by

Used with

Projects with it also use gws-events.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • JetBrainsSkill

    gws-events

    Subscribe to Google Workspace events.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

2 rules. 1 is common, 0 are distinctive, and 1 is very specific to this project.

  • 1

    Common

    Most of the 4 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Common:

    Before calling any API method, inspect it:

    line 98
  2. Very specific:

    Use gws schema output to build your --params and --json flags.

    line 108

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

calendar (v3)

PREREQUISITE: Read ../gws-shared/SKILL.md for auth, global flags, and security rules. If missing, run gws generate-skills to create it.

gws calendar <resource> <method> [flags]

Helper Commands

CommandDescription
+insertcreate a new event
+agendaShow upcoming events across all calendars

API Resources

acl

  • delete — Deletes an access control rule.
  • get — Returns an access control rule.
  • insert — Creates an access control rule.
  • list — Returns the rules in the access control list for the calendar.
  • patch — Updates an access control rule. This method supports patch semantics.
  • update — Updates an access control rule.
  • watch — Watch for changes to ACL resources.

calendarList

  • delete — Removes a calendar from the user's calendar list.
  • get — Returns a calendar from the user's calendar list.
  • insert — Inserts an existing calendar into the user's calendar list.
  • list — Returns the calendars on the user's calendar list.
  • patch — Updates an existing calendar on the user's calendar list. This method supports patch semantics.
  • update — Updates an existing calendar on the user's calendar list.
  • watch — Watch for changes to CalendarList resources.

calendars

  • clear — Clears a primary calendar. This operation deletes all events associated with the primary calendar of an account.
  • delete — Deletes a secondary calendar. Use calendars.clear for clearing all events on primary calendars.
  • get — Returns metadata for a calendar.
  • insert — Creates a secondary calendar. The authenticated user for the request is made the data owner of the new calendar.

Note: We recommend to authenticate as the intended data owner of the calendar. You can use domain-wide delegation of authority to allow applications to act on behalf of a specific user. Don't use a service account for authentication. If you use a service account for authentication, the service account is the data owner, which can lead to unexpected behavior.

  • patch — Updates metadata for a calendar. This method supports patch semantics.
  • update — Updates metadata for a calendar.

channels

  • stop — Stop watching resources through this channel

colors

  • get — Returns the color definitions for calendars and events.

events

  • delete — Deletes an event.
  • get — Returns an event based on its Google Calendar ID. To retrieve an event using its iCalendar ID, call the events.list method using the iCalUID parameter.
  • import — Imports an event. This operation is used to add a private copy of an existing event to a calendar. Only events with an eventType of default may be imported. Deprecated behavior: If a non-default event is imported, its type will be changed to default and any event-type-specific properties it may have will be dropped.
  • insert — Creates an event.
  • instances — Returns instances of the specified recurring event.
  • list — Returns events on the specified calendar.
  • move — Moves an event to another calendar, i.e. changes an event's organizer. Note that only default events can be moved; birthday, focusTime, fromGmail, outOfOffice and workingLocation events cannot be moved.
  • patch — Updates an event. This method supports patch semantics.
  • quickAdd — Creates an event based on a simple text string.
  • update — Updates an event.
  • watch — Watch for changes to Events resources.

freebusy

  • query — Returns free/busy information for a set of calendars.

settings

  • get — Returns a single user setting.
  • list — Returns all user settings for the authenticated user.
  • watch — Watch for changes to Settings resources.

Discovering Commands

Before calling any API method, inspect it:

# Browse resources and methods
gws calendar --help

# Inspect a method's required params, types, and defaults
gws schema calendar.<resource>.<method>

Use gws schema output to build your --params and --json flags.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.