🎯

google-calendar

🎯Skill

from team-attention/plugins-for-claude-natives

VibeIndex|
What it does

Enables multi-account Google Calendar integration, allowing parallel calendar querying and detecting scheduling conflicts across different calendars.

πŸ“¦

Part of

team-attention/plugins-for-claude-natives(10 items)

google-calendar

Installation

Add MarketplaceAdd marketplace to Claude Code
/plugin marketplace add team-attention/plugins-for-claude-natives
Install PluginInstall plugin from marketplace
/plugin install <plugin-name>
πŸ“– Extracted from docs: team-attention/plugins-for-claude-natives
1Installs
-
AddedFeb 4, 2026

Skill Details

SKILL.md

Overview

# Plugins for Claude Natives

A collection of Claude Code plugins for power users who want to extend Claude Code's capabilities beyond the defaults.

Table of Contents

  • [Quick Start](#quick-start)
  • [Available Plugins](#available-plugins)
  • [Plugin Details](#plugin-details)

- [agent-council](#agent-council) - Get consensus from multiple AI models

- [clarify](#clarify) - Transform vague requirements into specs

- [dev](#dev) - Community scanning + technical decision-making

- [doubt](#doubt) - Force Claude to re-validate responses

- [interactive-review](#interactive-review) - Review plans with a web UI

- [say-summary](#say-summary) - Hear responses via text-to-speech

- [youtube-digest](#youtube-digest) - Summarize and quiz on YouTube videos

- [gmail](#gmail) - Multi-account Gmail integration

- [google-calendar](#google-calendar) - Multi-account calendar integration

- [kakaotalk](#kakaotalk) - Send/read KakaoTalk messages on macOS

- [session-wrap](#session-wrap) - Session wrap-up + history analysis toolkit

  • [Contributing](#contributing)
  • [License](#license)

---

Quick Start

```bash

# Add this marketplace to Claude Code

/plugin marketplace add team-attention/plugins-for-claude-natives

# Install any plugin

/plugin install

```

---

Available Plugins

| Plugin | Description |

|--------|-------------|

| [agent-council](./plugins/agent-council/) | Collect and synthesize opinions from multiple AI agents (Gemini, GPT, Codex) |

| [clarify](./plugins/clarify/) | Transform vague requirements into precise specifications through iterative questioning |

| [dev](./plugins/dev/) | Developer workflow: community opinion scanning and technical decision analysis |

| [doubt](./plugins/doubt/) | Force Claude to re-validate its response when !rv is in your prompt |

| [interactive-review](./plugins/interactive-review/) | Interactive markdown review with web UI for visual plan/document approval |

| [say-summary](./plugins/say-summary/) | Speaks a short summary of Claude's response using macOS TTS (Korean/English) |

| [youtube-digest](./plugins/youtube-digest/) | Summarize YouTube videos with transcript, insights, Korean translation, and quizzes |

| [gmail](./plugins/gmail/) | Multi-account Gmail integration with email reading, searching, sending, and management |

| [google-calendar](./plugins/google-calendar/) | Multi-account Google Calendar integration with parallel querying and conflict detection |

| [kakaotalk](./plugins/kakaotalk/) | Send and read KakaoTalk messages on macOS using Accessibility API |

| [session-wrap](./plugins/session-wrap/) | Session wrap-up, history analysis, and session validation toolkit |

Plugin Details

agent-council

![Demo](./assets/agent-council.gif)

Summon multiple AI models to debate your question and reach a consensus.

When you're facing a tough decision or want diverse perspectives, this plugin queries multiple AI agents (Gemini CLI, GPT, Codex) in parallel and synthesizes their opinions into a single, balanced answer.

Trigger phrases:

  • "summon the council"
  • "ask other AIs"
  • "what do other models think?"

How it works:

  1. Your question is sent to multiple AI agents simultaneously
  2. Each agent provides its perspective
  3. Claude synthesizes the responses into a consensus view with noted disagreements

```bash

# Example

User: "summon the council - should I use TypeScript or JavaScript for my new project?"

```

---

clarify

![Demo](./assets/clarify.gif)

Turn vague requirements into precise, actionable specifications.

Before writing code based on ambiguous instructions, this plugin conducts a structured interview to extract exactly what you need. No more assumptions, no more rework.

Trigger phrases:

  • "/clarify"
  • "clarify requirements"
  • "what do I mean by..."

The process:

  1. Capture - Record the original requirement verbatim
  2. Question - Ask targeted multiple-choice questions to resolve ambiguities
  3. Compare - Present before/after showing the transformation
  4. Save - Optionally save the clarified spec to a file

Example transformation:

| Before | After |

|--------|-------|

| "Add a login feature" | Goal: Add username/password login with self-registration. Scope: Login, logout, registration, password reset. Constraints: 24h session, bcrypt, rate limit 5 attempts. |

---

dev

Developer workflow tools: community scanning and technical decision-making.

This plugin provides two powerful skills for developer research and decision-making.

#### Skills

/dev-scan - Scan developer communities for real opinions

  • Searches Reddit (via Gemini CLI), Hacker News, Dev.to, and Lobsters in parallel
  • Synthesizes consensus, controversies, and notable perspectives
  • Great for understanding community sentiment before adopting a tool

/tech-decision - Deep technical decision analysis

  • Multi-phase workflow with 4 specialized agents running in parallel
  • Combines codebase analysis, docs research, community opinions, and AI perspectives
  • Produces executive-summary-first reports with scored comparisons

Trigger phrases:

  • "developer reactions to...", "what do devs think about..."
  • "A vs B", "which library should I use", "기술 μ˜μ‚¬κ²°μ •"

How tech-decision works:

```

Phase 1: Parallel Information Gathering

β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”

β”‚ codebase- β”‚ docs- β”‚ dev-scan β”‚ agent-council β”‚

β”‚ explorer β”‚ researcher β”‚ (community) β”‚ (AI experts) β”‚

β””β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”΄β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”΄β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”΄β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”˜

β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”΄β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”΄β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

β”‚

Phase 2: Analysis & Synthesis β–Ό

β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”

β”‚ tradeoff-analyzer β”‚

β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

β”‚

β–Ό

β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”

β”‚ decision-synthesizer β”‚

β”‚ (Executive Summary First) β”‚

β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

```

```bash

# Examples

User: "React vs Vue for my new project?"

User: "Which state management library should I use?"

User: "Monolith vs microservices for our scale?"

```

---

doubt

Force Claude to double-check its response before delivering.

When you include !rv anywhere in your prompt, Claude will pause before responding, re-validate its answer against potential errors, and only then deliver the response. Perfect for critical decisions or when you want extra confidence.

Trigger:

  • Include !rv anywhere in your prompt

How it works:

  1. UserPromptSubmit hook detects !rv keyword and sets a flag
  2. Stop hook intercepts Claude's response before delivery
  3. Claude re-validates the response for errors, hallucinations, or questionable claims
  4. Only after verification does Claude deliver the final answer

Why !rv instead of !doubt?

The word "doubt" affects Claude's behavior - it starts doubting from the beginning. !rv (re-validate) is neutral.

```bash

# Example

User: "What's the time complexity of binary search? !rv"

# Claude will verify its answer before responding

```

---

interactive-review

Review Claude's plans and documents through a visual web interface.

Instead of reading long markdown in the terminal, this plugin opens a browser-based UI where you can check/uncheck items, add comments, and submit structured feedback.

Trigger phrases:

  • "/review"
  • "review this plan"
  • "let me check this"

The flow:

  1. Claude generates a plan or document
  2. A web UI opens automatically in your browser
  3. Review each item with checkboxes and optional