Skip to content
Agentmart
Submit a tool

calendar-setup

Step-by-step setup and troubleshooting for connecting an owner's Google Calendar to an OpenClaw agent with read and write access.

Skill by netanel-abergel

IndexedMIT★ 6
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/netanel-abergel-calendar-setup

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Step-by-step setup and troubleshooting for connecting an owner's Google Calendar to an OpenClaw agent with read and write access. Use when: setting up calendar access for the first time, fixing read-only access, re-authenticating a broken Google connection, explaining the difference between the owner's Google account and the agent's Google account, how an OpenClaw agent accesses Gmail or Google Workspace, where credentials are stored, how to use the agent inbox, how to give the agent write access to the owner's calendar, or guiding another agent or user through the email or calendar setup model.

Use cases: writing, productivity, agent-building

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/calendar-setup

What's inside

Skill name
calendar-setup
Description
Step-by-step setup and troubleshooting for connecting an owner's Google Calendar to an OpenClaw agent with read and write access. Use when: setting up calendar access for the first time, fixing read-only access, re-authenticating a broken Google connection, explaining the difference between the owner's Google account and the agent's Google account, how an OpenClaw agent accesses Gmail or Google Workspace, where credentials are stored, how to use the agent inbox, how to give the agent write access to the owner's calendar, or guiding another agent or user through the email or calendar setup model.
License
MIT
Instructions
210 lines in SKILL.md · view on GitHub

Before installing

  • Instructions call the network
  • Instructions read files in your home folder (~/.ssh, ~/.aws…)

Files (1)

  • SKILL.md

SKILL.md (first lines)

# Calendar Setup

Use this skill when calendar access needs to be established or repaired.

## Core model

Treat these as separate identities:
- **Owner account**: the human's Google account and calendar
- **Agent account**: the PA's own Google account

The agent does not get calendar access automatically. The owner must share access, and the agent must authenticate the relevant Google account in `gog`.

## Standard setup

### 1. Owner shares the calendar

The owner should do this in Google Calendar:
1. Open `calendar.google.com`
2. Open the primary calendar's **Settings and sharing**
3. Under **Share with specific people**, add the agent email
4. Grant **Make changes to events**

If external sharing is blocked, the owner's Google Workspace admin has to allow it.

### 2. Authenticate with `gog`

```bash
gog auth add owner@company.com --services gmail,calendar,drive,contacts
gog auth list
```

Use the actual owner email. If a stale auth entry exists:

```bash
gog auth remove owner@company.com
gog auth add owner@company.com --services gmail,calendar,drive,contacts
```

### 3. Verify write access

```bash
START=$(date -u -d '+1 hour' +%Y-%m-%dT%H:%M:%SZ 2>/dev/null || date -u -v+1H +%Y-%m-%dT%H:%M:%SZ)
END=$(date -u -d '+2 hours' +%Y-%m-%dT%H:%M:%SZ 2>/dev/null || date -u -v+2H +%Y-%m-%dT%H:%M:%SZ)

GOG_ACCOUNT=owner@company.com gog calendar create primary \
  --summary "PA setup test, delete me" \
  --start "$START" \
  --end "$END"
```

Then confirm the event appears in the owner's calendar and delete it.

## Troubleshooting order

Work in this order:
1. Confirm whether the problem is about the owner account or the agent account.
2. Run `gog auth list` and confirm the needed account exists.
3. Confirm the shared calendar permission is **Make changes to events**.
4. Use `GOG_ACCOUNT=owner@company.com` explicitly in commands.
5. Retry after `gog auth remove` + `gog auth add` if auth is stale.

## Common failures

### Dashboard says connected, but writes fail
The dashboard may reflect the agent's own Google connection, not the owner's calendar permission. Re-check sharing and `GOG_ACCOUNT`.

### Insufficient permissions
The calendar was shared read-only. Re-share with **Make changes to events**.

### No browser or interactive auth is unavailable
Use an already-provisioned `gog` account if one exists. If no valid Google auth is available on the host, stop and report that manual re-authentication is required.

### Multiple calendars
Authenticate each account separately and use the specific calendar ID from:

```bash
GOG_ACCOUNT=owner@company.com gog calendar list
```

## Verification checklist

- [ ] Owner shared the correct calendar with the agent email
- [ ] Permission is `Make changes to events`
- [ ] `gog auth list` shows the required account
- [ ] Commands use explicit `GOG_ACCOUNT=...`
- [ ] A test event can be created and deleted

## Notes

- Do not print OAuth secrets or credential file contents in chat.
- Prefer the shortest path that restores working read/write calendar access.
- If the issue is really about Gmail or Drive access, switch to the `gog` skill after clarifying the exact service.

---

## Email Model Appendix

*(Absorbed from `openclaw-email-orientation` on 2026-05-09.)*

### Minimum Model
Any model. This appendix is explanation and troubleshooting only — no complex reasoning needed.

### The Core Concept

There are two separate accounts:

| | Account |
|---|---|
| **Owner** | The human's Google account (e.g. `owner@company.com`) |
| **Agent** | The PA's own Google account (e.g. `agent@agentdomain.com`) |

These are separate. Having an agent email does NOT automatically give access to the owner's email or calendar. To access the owner's email/calendar: (1) owner must share access with the agent email, and (2) agent must authenticate using `gog`.

### Key Paths and Files

| File | Purpose |
|---|---|
| `~/.openclaw/.gog/credentials.json` | gog OAuth client credentials |
| `~/.openclaw/agents/main/agent/auth-profiles.json` | OpenClaw auth profiles |

From netanel-abergel/pa-skills, MIT.

More from netanel-abergel/pa-skills

Signals

Stars
6
Forks
1
Open issues
0
Last commit (this folder)
May 9, 2026 (5 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from netanel-abergel

Cite this page

calendar-setup skill. Agent Mart. https://agentmart.dev/skills/netanel-abergel-calendar-setup (last updated 2026-10-24)