← Back to Skills Marketplace
Calendar Local
by
JULIAN GOMEZ FERNANDEZ
· GitHub ↗
· v1.0.0
· MIT-0
117
Downloads
0
Stars
1
Active Installs
1
Versions
Install in OpenClaw
/install calendar-local
Description
Read Google Calendar from the local host using the configured gog wrapper. Use when the user asks for their agenda, calendar events, today's schedule, this w...
README (SKILL.md)
Calendar Local
Use the local wrapper instead of generic calendar advice.
Commands
Run the wrapper with an explicit timeframe:
/home/ubuntu/.openclaw/workspace/.openclaw/calendar.sh today
/home/ubuntu/.openclaw/workspace/.openclaw/calendar.sh week
/home/ubuntu/.openclaw/workspace/.openclaw/calendar.sh days 7
The wrapper already targets the correct Google account and gog binary. It requires GOG_KEYRING_PASSWORD in the runtime environment.
Workflow
- Run the wrapper with the matching timeframe.
- If the user asked for today, use
today. - If the user asked for this week, use
week. - If the user asked for the next few days, use
days N. - Summarize results in natural language.
- If no events match, say so plainly.
- Do not tell the user to configure OAuth again unless the wrapper fails.
Failure handling
If the wrapper fails:
- If output mentions
GOG_KEYRING_PASSWORD is not set, explain that the OpenClaw service is missing the keyring password in its environment. - If output mentions keyring unlock/auth errors, explain that the local Google token/keyring is unavailable or locked.
- Only then fall back to setup guidance.
Output style
- Be concise.
- Prefer grouped agenda summaries.
- Separate all-day items, timed events, and birthdays/tasks when useful.
Usage Guidance
This skill will run a local script at /home/ubuntu/.openclaw/workspace/.openclaw/calendar.sh and expects the service to have GOG_KEYRING_PASSWORD set. Before installing, verify the following: (1) confirm the calendar.sh wrapper is present and inspect its contents to ensure it does only what you expect (reading calendar via gog) and does not exfiltrate data; (2) ensure GOG_KEYRING_PASSWORD is stored and provided securely — the skill metadata should explicitly declare this env var and the required config path; (3) if you cannot inspect or verify the wrapper, do not enable the skill — it could expose local tokens/credentials; and (4) ask the publisher to update the skill registry entry to list the required config path and GOG_KEYRING_PASSWORD so the requirement is explicit. If you intend to use this on a shared host or in an environment where the agent can be invoked autonomously, be extra cautious because the wrapper and the keyring password are sensitive.
Capability Analysis
Type: OpenClaw Skill
Name: calendar-local
Version: 1.0.0
The skill bundle facilitates local Google Calendar access by executing a shell script at a hardcoded path (/home/ubuntu/.openclaw/workspace/.openclaw/calendar.sh). It is classified as suspicious due to a potential shell injection vulnerability in the 'days N' command workflow, where the variable 'N' is derived from user input without explicit sanitization instructions in SKILL.md. While the use of the GOG_KEYRING_PASSWORD environment variable is consistent with the stated purpose, the reliance on an external, unprovided script and the lack of input validation pose a security risk.
Capability Assessment
Purpose & Capability
The SKILL.md behavior (running a local gog wrapper at /home/ubuntu/.openclaw/workspace/.openclaw/calendar.sh to read Google Calendar) matches the skill description, but the registry metadata does not declare the required config path or the GOG_KEYRING_PASSWORD env var the instructions explicitly expect. The hard-coded path and password requirement should have been declared.
Instruction Scope
Instructions are narrowly scoped to running the local wrapper with timeframe arguments and summarizing output. They do not request unrelated files or network endpoints. However, they explicitly rely on a local file path and an environment secret and include guidance to interpret keyring/unlock errors — which increases sensitivity of what the agent will access.
Install Mechanism
There is no install spec and no code files — this is instruction-only, so nothing is written to disk by the skill itself. That reduces install-time risk.
Credentials
SKILL.md requires GOG_KEYRING_PASSWORD in the runtime environment and access to a specific user path, but the skill's declared requirements list no env vars or config paths. Asking for a password-like env var without declaring it is disproportionate and opaque. The env var is sensitive and should be explicitly declared and justified in metadata.
Persistence & Privilege
The skill is not always-enabled and does not request system-wide changes. It will run only when invoked. No other elevated persistence is requested.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install calendar-local - After installation, invoke the skill by name or use
/calendar-local - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
- Initial release of the calendar-local skill.
- Enables reading Google Calendar events directly from the local host using a pre-configured shell wrapper.
- Supports natural language queries for today's agenda, weekly events, upcoming appointments, and calendar summaries.
- Integrates with OpenClaw, requiring access to a specific script and environment password (GOG_KEYRING_PASSWORD).
- Includes robust error handling for missing credentials or keyring issues.
- Provides concise, grouped summaries of events, separating all-day and timed items when relevant.
Metadata
Frequently Asked Questions
What is Calendar Local?
Read Google Calendar from the local host using the configured gog wrapper. Use when the user asks for their agenda, calendar events, today's schedule, this w... It is an AI Agent Skill for Claude Code / OpenClaw, with 117 downloads so far.
How do I install Calendar Local?
Run "/install calendar-local" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Calendar Local free?
Yes, Calendar Local is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Calendar Local support?
Calendar Local is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Calendar Local?
It is built and maintained by JULIAN GOMEZ FERNANDEZ (@jgf78); the current version is v1.0.0.
More Skills