AgentStack
Sign in Publish
MCP servers Skills Toolkits Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Google Calendar Cli

skill-batteryshark-skill-tap-google-calendar-cli · by batteryshark

Authenticate a desktop Google Calendar client, inspect calendars and events, query free/busy data, and create or delete events through a reviewable plan with hash-bound explicit confirmation. Use when a user wants direct Google Calendar CLI automation without an MCP server.

↗ Repository
— No reviews yet
0 installs
5 views
0.0% view→install

Install

$ agentstack add skill-batteryshark-skill-tap-google-calendar-cli

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Google Calendar Cli? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Google Calendar CLI

Use bin/google-calendar-cli. Read operations execute directly. Calendar mutations require a plan file and the exact confirmation hash printed during planning.

Workflow

  1. Read [references/setup-and-confirmation.md](references/setup-and-confirmation.md).
  2. Authenticate once with the required account.
  3. Use read commands to resolve calendar IDs, event IDs, dates, and time zones.
  4. Generate a create or delete plan.
  5. Show the complete plan to the user, including attendees and notification behavior.
  6. Only after explicit approval, run apply-plan --confirm .
  7. Relay the returned event ID and link or deletion result.

Never infer approval from the original scheduling request. A calendar mutation needs confirmation after the concrete plan exists.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in Productivity