google-calendar-automation
Automate Google Calendar from Local Commands
Manual calendar updates and availability checks consume time and cause scheduling errors. This skill provides structured command guidance for Google Workspace calendar tasks.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "google-calendar-automation" from https://skillstore.io/skills/sickn33-google-calendar-automation.md and its manifest at https://skillstore.io/api/skills/sickn33-google-calendar-automation/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "google-calendar-automation". Show my next three events from the primary calendar.
Expected outcome:
- Project review: July 27, 14:00 to 14:30 UTC
- Design sync: July 28, 09:00 to 10:00 UTC
- Planning session: July 29, 16:00 to 17:00 UTC
Using "google-calendar-automation". Find a 30-minute opening for Alex and Morgan tomorrow afternoon.
Expected outcome:
The first shared opening is tomorrow from 14:30 to 15:00 UTC. No event has been created.
Using "google-calendar-automation". Prepare a team review for Friday at 10:00 UTC.
Expected outcome:
Ready to create Team Review on Friday from 10:00 to 11:00 UTC. Please confirm the attendees and calendar.
Security Audit
Medium RiskAll 27 static findings are false positives caused by Markdown fences or inline literals; SKILL.md contains no Ruby or shell backtick execution. However, the document directs users to missing Python scripts that would handle OAuth credentials and calendar changes, so the security-sensitive implementation cannot be audited.
Confirmed security concerns (1)
Risk Factors
⚙️ External commands (27)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/sickn33-google-calendar-automation/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/sickn33-google-calendar-automation?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/sickn33-google-calendar-automation?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-google-calendar-automation/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/sickn33-google-calendar-automation.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
sickn33. (2026). google-calendar-automation security audit report (audit version 5) [Author version 1.0]. Skillstore. https://skillstore.io/skills/sickn33-google-calendar-automation/audits/5BibTeX citation
@techreport{sickn33-sickn33-google-calendar-automation-2026,
author = {sickn33},
title = {google-calendar-automation security audit report (audit version 5)},
institution = {Skillstore},
year = {2026},
number = {5},
url = {https://skillstore.io/skills/sickn33-google-calendar-automation/audits/5},
note = {Author version 1.0}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "google-calendar-automation security audit report (audit version 5)"
version: "1.0"
type: report
authors:
- name: "sickn33"
date-released: "2026-07-24"
url: "https://skillstore.io/skills/sickn33-google-calendar-automation/audits/5"
identifiers:
- type: other
value: "skillstore:sickn33-google-calendar-automation:audit:5"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Coordinate Team Meetings
Find shared availability and prepare a meeting with attendees, location, and an agenda.
Maintain Operational Calendars
List, inspect, create, update, or remove events on a selected Workspace calendar.
Process Calendar Invitations
Review an event and prepare an accepted, declined, or tentative response.
Try These Prompts
Show my next ten events from the primary calendar. Use UTC and do not change any events.
Get details for event [EVENT_ID] on calendar [CALENDAR_ID]. Summarize the time, attendees, location, and description.
Prepare a [DURATION]-minute event titled [TITLE] between [START] and [END] for [ATTENDEES]. Ask before creating it.
Find the first [DURATION]-minute opening for [ATTENDEES] between [START] and [END]. Present the slot, then request confirmation before creating [TITLE].
Best Practices
- Use explicit ISO 8601 timestamps with timezone offsets.
- Review the target calendar, attendees, and time range before making changes.
- Request confirmation before creating, updating, deleting, or responding to events.
Avoid
- Do not run commands until the missing scripts and dependencies are verified.
- Do not omit timezone information or assume the user's local timezone.
- Do not expose OAuth tokens, calendar identifiers, or attendee details in logs.
Frequently Asked Questions
Does this skill require an MCP server?
Can I use a personal Gmail account?
Can it create and change calendar events?
Can it find shared availability?
How are OAuth tokens stored?
What time format should I use?
Developer Details
Author
sickn33License
Apache-2.0
Author version
v1.0
Skillstore revision
r2
Version notice
The author-declared version is not valid SemVer.
Repository
https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/google-calendar-automationRef
88a8e9a07f4c54ab105c1c41b6267c287146b07b
Maintenance freshness
7/26/2026
Usage
6 downloads · 90 views
File structure
📄 SKILL.md