add-skill-gmail

Configure Gmail OAuth scopes and sync credentials for NanoClaw agents.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/TerrifiedBug/nanoclaw-skills --skill add-skill-gmail
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-skill-gmail
Source: https://github.com/TerrifiedBug/nanoclaw-skills/tree/main/plugins/nanoclaw-gmail/skills/add-skill-gmail
Command: npx skills add https://github.com/TerrifiedBug/nanoclaw-skills --skill add-skill-gmail

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Gmail access for NanoClaw empowers agent containers to search, read, and send emails by configuring the Gmail API through the gog CLI, and it shares credentials with Google Calendar when a Calendar setup is already in place.

Core Features & Use Cases

  • OAuth-driven Gmail access for agent containers and per-group scoping.
  • Unified credentials syncing with existing Calendar configurations to streamline setup.
  • End-to-end setup guidance from installation to container restart, covering per-group access control and channel considerations.

Quick Start

Enable Gmail integration for your workspace and follow the prompts to configure OAuth scopes, authorize access, and sync credentials.

Frequently Asked Questions about add-skill-gmail

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enable Gmail API access for my AI agents?

You enable Gmail API access by configuring OAuth scopes and linking Google Cloud project credentials to your agent containers, allowing them to search, read, and send emails.

Can I use my existing Google Calendar credentials for Gmail integration?

Yes, you can use existing Google Calendar credentials for Gmail integration. The setup uses unified credential syncing to share credentials across both Calendar and Gmail services.

What do I need to set up Gmail OAuth for multi-group agent containers?

Setting up Gmail OAuth requires the gog CLI, a Google Cloud project with Gmail API enabled, and credential synchronization to the data/gogcli directory for per-group scoping.

How does per-group credential scoping work for Gmail access?

Per-group credential scoping isolates OAuth authorization for specific groups within multi-group environments. It ensures each group accesses Gmail using independently synced credentials.

Why are my Gmail credentials not working inside the agent container?

Gmail credentials fail inside agent containers when synchronization to the data/gogcli directory is incomplete. You must sync credentials properly and restart the container to apply changes.