google-calendar-mcp is an MCP server that lets AI assistants connect to Google Calendar and manage calendar information. It supports tasks such as searching, creating, updating, and deleting events, checking availability, handling recurring events, and detecting conflicts across calendars. The catalogue skills, instructions, commands, and agents provide workflows for operating this integration.
Borrowing it
Nothing to install: this file belongs to nspady/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/nspady/google-calendar-mcp/main/.claude/skills/triage-prs/SKILL.mdgit clone --depth 1 https://github.com/nspady/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/nspady/google-calendar-mcp/triage-prs)<a href="https://agentmods.dev/skills/nspady/google-calendar-mcp/triage-prs"><img src="https://agentmods.dev/badge/skills/nspady/google-calendar-mcp/triage-prs/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/nspady/google-calendar-mcp/triage-prs"><img src="https://agentmods.dev/badge/skills/nspady/google-calendar-mcp/triage-prs.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.00080 | $0.00700 |
| Opus 5.5 | $0.00032 | $0.00280 |
| Sonnet 5.5 | $0.00016 | $0.00140 |
| Haiku 4.5 | $0.00008 | $0.00070 |
Grade A, and why
triage-prs 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 20d 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.
How it starts
The opening of the file, as written. The whole thing — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR triage
Status sweep
For each open PR: state, head SHA drift since last look, new comments or
review-thread replies (check pulls/<n>/comments too — thread replies don't
bump the issue comment list), mergeable state, and author responsiveness.
Note that a PR's updatedAt bumps on the maintainer's own review activity;
verify who acted before reporting it as author movement.
Nudges and deadline closes
- Nudge template (tag the author): "Checking in, any chance you'll have time to address the review feedback? I'll close this in a week if I don't hear back, happy to reopen anytime."
- Record the deadline (one week from the nudge timestamp).
- When the deadline passes, the close must be gated: re-verify there has been no author activity since the nudge before closing. Close message: "Closing this for now since I haven't heard back, happy to reopen if you get a chance to pick it up again. Thanks for the contribution!"
- Never close a PR that the maintainer approved; that one is waiting on the maintainer, not the author.
Adopt or close an abandoned PR
Before taking over an abandoned PR, weigh:
- Demand: are there issues or discussions asking for this? Zero demand argues for closing.
- Surface symmetry: does the tool fit the existing API surface (e.g. a delete-X with no create-X is a flag)?
- Blast radius: destructive operations carry permanent ownership cost and model-misuse risk; the bar is higher.
- Review debt: how many of the review findings would adoption require implementing from scratch?
If adopting: rebase in a scratch clone, keep the author's commits and authorship, implement the review asks as separate commits, run the full suite. Maintainer pushes to org-owned forks are rejected by GitHub even with "allow edits" on, so when the fork is org-owned, land via a fresh PR from an origin branch (rebase-merge to preserve authorship) and close the original with a comment crediting the author and linking the landing PR.
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.
- 20d ago First seen · 67 lines · 80 tokens per session scan A 54f0717cd307
triage-prs is a skill published in the GitHub repository nspady/google-calendar-mcp (1,206 stars, last pushed yesterday), licensed MIT. It adds 80 tokens to every session and 700 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-09.
Other skills, from other repositories
antfu-issue-triage
Triage open issues and PRs of the current GitHub repo - find already-fixed, duplicate, and spam items, suggest labels, gauge demand from reactions and comments, then present a table of proposed actions and comments for confirmation before touching anything. Use when asked to triage, organize, clean up, or groom issues…
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
engineer-bot-ops
A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
connect
Choose which wiki this session uses, the team project's pages on the Nimbalyst server or the project's local wiki of files, and connect a repository to its team project. Use at the start of a task before any wiki tool, when a wiki tool returns reponotbound, ambiguousproject, pinmismatch, projectnotaccessible…
llxprt-issue-workflow
Use this skill when asked to address, fix, or work on a GitHub issue in the llxprt-code repository. Covers the complete issue lifecycle - branch setup, gh CLI usage, test-first planning, subagent delegation and review loops, the full verification cycle (including the zai-glm-flash smoke test), open code review (ocr)…