Gws Calendar Agenda

Google Calendar: Show upcoming events across all calendars.

Security Scan

The skill's declared purpose (show calendar events) matches its visible instructions, but it hides crucial auth/global-flag requirements in an external gws-shared SKILL.md that is not included — creating an opaque dependency that may request credentials or file access.

Purpose & Capability

The skill name/description and the only required binary ('gws') align: it simply runs the gws CLI to show calendar agenda. There are no unrelated binaries or environment variables declared in the package itself.

Instruction Scope

The runtime instructions explicitly defer auth, global flags, and security rules to ../gws-shared/SKILL.md (or to generate it with `gws generate-skills`). That external dependency is not included, so the actual authorization flow, what files or tokens are read/written, and any global flags are hidden from review. This makes it impossible to confirm the skill stays within its stated read-only scope.

Install Mechanism

Instruction-only skill (no install spec, no code files). Nothing will be written during install by the skill itself. The only runtime requirement is the external 'gws' CLI binary, which should be inspected separately.

Credentials

This package declares no required env vars or credentials, which is consistent with a simple read-only agenda command. However, because auth details are delegated to gws-shared (not included), the skill may implicitly require Google auth tokens, config files, or other environment variables — those are not visible here and therefore not verifiable.

Persistence & Privilege

No 'always: true' or other elevated persistence is requested. The skill is user-invocable and can be called autonomously (platform default), which is normal and expected for a CLI-invoking skill.

What to consider before installing

This SKILL.md itself is small and coherent: it runs the 'gws' CLI to show events. The unknown piece is ../gws-shared/SKILL.md, which the skill points to for authentication and global flags. Before installing or enabling this skill you should: 1) Inspect the gws-shared SKILL.md (or the output of `gws generate-skills`) to see exactly what auth flow and files it uses — e.g., OAuth client IDs, refresh tokens, credentials stored on disk, or ENV vars. 2) Verify the provenance of the 'gws' binary (where it came from, checksums, maintainers). 3) Confirm that any auth scopes are read-only and limited to calendar access. 4) If you cannot view gws-shared, treat the dependency as opaque and avoid providing broad Google credentials; consider running the gws CLI in an isolated environment or container. If you provide the gws-shared SKILL.md or details of the gws CLI auth flow, I can re-evaluate and raise or lower the concern level.

calendar +agenda

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

Show upcoming events across all calendars

Usage

gws calendar +agenda

Flags

Flag	Required	Default	Description
--today	—	—	Show today's events
--tomorrow	—	—	Show tomorrow's events
--week	—	—	Show this week's events
--days	—	—	Number of days ahead to show
--calendar	—	—	Filter to specific calendar name or ID
--timezone	—	—	IANA timezone override (e.g. America/Denver). Defaults to Google account timezone.

Examples

gws calendar +agenda
gws calendar +agenda --today
gws calendar +agenda --week --format table
gws calendar +agenda --days 3 --calendar 'Work'
gws calendar +agenda --today --timezone America/New_York

Tips

• Read-only — never modifies events.
• Queries all calendars by default; use --calendar to filter.
• Uses your Google account timezone by default; override with --timezone.

See Also

• gws-shared — Global flags and auth
• gws-calendar — All manage calendars and events commands