Borrowing it
Nothing to install: this file belongs to 84emllc/google-calendar-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/84emllc/google-calendar-mcp/main/.claude/skills/gcal-api-research/SKILL.mdgit clone --depth 1 https://github.com/84emllc/google-calendar-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/84emllc/google-calendar-mcp/gcal-api-research)<a href="https://agentmods.dev/skills/84emllc/google-calendar-mcp/gcal-api-research"><img src="https://agentmods.dev/badge/skills/84emllc/google-calendar-mcp/gcal-api-research/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/84emllc/google-calendar-mcp/gcal-api-research"><img src="https://agentmods.dev/badge/skills/84emllc/google-calendar-mcp/gcal-api-research.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00082 | $0.02928 |
| Opus 5 | $0.00041 | $0.01464 |
| Sonnet 5 | $0.00016 | $0.00586 |
| Haiku 4.5 | $0.00008 | $0.00293 |
Grade A, and why
gcal-api-research scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
This is a copy
100% identical to gcal-api-research — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 343 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Google Calendar API Research
Quick Start
What are you doing?
- 📝 Reviewing a PR → Read
references/research-checklist.mdfirst - 🚀 Planning a feature → Start with Step 1 below, then consult relevant references
- 🐛 Investigating an issue → Check
references/edge-cases.mdfor known pitfalls - ✅ Validating an approach → Read
references/api-patterns.mdfor best practices
Then follow the detailed workflow below.
Overview
This skill provides a structured approach to researching Google Calendar API implementations, identifying best practices, and uncovering potential edge cases. Use this skill to ensure implementations leverage Google Calendar APIs appropriately with good defaults while supporting complex use cases.
When to Use This Skill
Use this skill when:
- Reviewing PRs that add new Google Calendar functionality (e.g., "feat: add respond-to-event tool")
- Planning new features before implementation begins
- Investigating issues with existing Google Calendar integrations
- Validating implementation approaches against Google Calendar API best practices
- Researching edge cases for specific calendar operations
This skill is particularly valuable for features involving:
- Recurring event handling
- Timezone conversions
- Batch operations across multiple calendars
- Event conflict detection
- Attendee management
- Conference data integration
Research Workflow
Step 1: Understand the Feature
First, identify what the implementation does or plans to do:
- For PR Reviews: Read the PR description and examine the code changes
- For Feature Planning: Clarify the requirements and desired functionality
- For Issues: Understand the reported problem and expected behavior
Key Questions:
- What Google Calendar API operations are involved?
- What user scenarios does this support?
- What are the critical requirements (performance, reliability, edge cases)?
Step 2: Consult Reference Materials
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 11d ago First seen · 343 lines · 82 tokens per session scan A 3d42c4f958b4
gcal-api-research is a skill published in the GitHub repository 84emllc/google-calendar-mcp (0 stars, last pushed 3mo ago), licensed MIT. It adds 82 tokens to every session and 2,928 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to gcal-api-research, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
design-mcp-server
Design the tool surface, resources, and service layer for a new MCP server. Use when starting a new server, planning a major feature expansion, or when the user describes a domain/API they want to expose via MCP. Produces a design doc at docs/design.md that drives implementation.
api-telemetry
Catalog of OpenTelemetry instrumentation built into framework @cyanheads/mcp-ts-core — spans, metrics, completion logs, env config, runtime caveats, custom instrumentation patterns, and cardinality rules. Use when enabling OTel export, adding custom spans or metrics in services, debugging missing telemetry, looking up…
api-mirror
Stand up a persistent, self-refreshing local mirror of a bulk upstream dataset with the MirrorService (@cyanheads/mcp-ts-core/mirror). Use when a server wraps a large or slow API and should query a synced local index (embedded SQLite + FTS5) instead of paginating the live API per request.
api-services
API reference for built-in service providers (LLM, Speech, Graph). Use when looking up service interfaces, provider capabilities, or integration patterns.
cmdb-patterns
Create ServiceNow CIs and cmdbrelci relationships, walk upstream/downstream impact, detect orphan/stale CIs, and align discovered CIs with the proper sysclassname hierarchy.
csm-patterns
Build ServiceNow Customer Service Management — customeraccount, customercontact, sncustomerservicecase routing, service entitlements with usage decrement, and Customer Portal case submission widgets.