google-docs
Create and modify Google Docs documents. Read content, insert tables, apply heading styles, and manage formatting. Use when asked to edit a gdoc, write a Google document, update a doc, or format document content.
What this skill does
# Google Docs
Interact with Google Docs for document creation, editing, and content management.
## Installation
**Dependencies**: `pip install --user google-auth google-auth-oauthlib google-api-python-client keyring pyyaml markdown`
## Setup Verification
After installation, verify the skill is properly configured:
```bash
$SKILL_DIR/scripts/google-docs.py check
```
This will check:
- Python dependencies (google-auth, google-auth-oauthlib, google-api-python-client, keyring, pyyaml, markdown)
- Authentication configuration
- Connectivity to Google Docs API
If anything is missing, the check command will provide setup instructions.
## Authentication
Google Docs uses OAuth 2.0 for authentication. For complete setup instructions, see:
1. [GCP Project Setup Guide](https://github.com/odyssey4me/agent-skills/blob/main/docs/gcp-project-setup.md) - Create project, enable Docs API
2. [Google OAuth Setup Guide](https://github.com/odyssey4me/agent-skills/blob/main/docs/google-oauth-setup.md) - Configure credentials
### Quick Start
1. Create `~/.config/agent-skills/google.yaml`:
```yaml
oauth_client:
client_id: your-client-id.apps.googleusercontent.com
client_secret: your-client-secret
```
2. Run `$SKILL_DIR/scripts/google-docs.py check` to trigger OAuth flow and verify setup.
On scope or authentication errors, see the [OAuth troubleshooting guide](https://github.com/odyssey4me/agent-skills/blob/main/docs/google-oauth-setup.md#troubleshooting).
## Commands
See [permissions.md](references/permissions.md) for read/write classification of each command.
### check
Verify configuration and connectivity.
```bash
$SKILL_DIR/scripts/google-docs.py check
```
This validates:
- Python dependencies are installed
- Authentication is configured
- Can connect to Google Docs API
- Creates a test document to verify write access
### auth setup
Store OAuth 2.0 client credentials for custom OAuth flow.
```bash
$SKILL_DIR/scripts/google-docs.py auth setup \
--client-id YOUR_CLIENT_ID \
--client-secret YOUR_CLIENT_SECRET
```
Credentials are saved to `~/.config/agent-skills/google-docs.yaml`.
**Options:**
- `--client-id` - OAuth 2.0 client ID (required)
- `--client-secret` - OAuth 2.0 client secret (required)
### auth reset
Clear stored OAuth token. The next command that needs authentication will trigger re-authentication automatically.
```bash
$SKILL_DIR/scripts/google-docs.py auth reset
```
Use this when you encounter scope or authentication errors.
### auth status
Show current OAuth token information without making API calls.
```bash
$SKILL_DIR/scripts/google-docs.py auth status
```
Displays: whether a token is stored, granted scopes, refresh token presence, token expiry, and client ID.
### documents create
Create a new blank Google Doc.
```bash
$SKILL_DIR/scripts/google-docs.py documents create --title "My Document"
```
**Options:**
- `--title` - Document title (required)
**Example:**
```bash
# Create a new document
$SKILL_DIR/scripts/google-docs.py documents create --title "Project Notes"
# Output:
# ✓ Document created successfully
# Title: Project Notes
# Document ID: 1abc...xyz
# URL: https://docs.google.com/document/d/1abc...xyz/edit
```
### documents get
Get document metadata and structure.
```bash
$SKILL_DIR/scripts/google-docs.py documents get DOCUMENT_ID
```
**Arguments:**
- `document_id` - The Google Docs document ID
**Example:**
```bash
# Get document metadata
$SKILL_DIR/scripts/google-docs.py documents get 1abc...xyz
# Output:
# Title: Project Notes
# Document ID: 1abc...xyz
# Characters: 1234
# Revision ID: abc123
```
### documents read
Read document content as plain text, markdown, or PDF.
```bash
$SKILL_DIR/scripts/google-docs.py documents read DOCUMENT_ID
```
**Arguments:**
- `document_id` - The Google Docs document ID
**Options:**
- `--format` - Output format: `markdown` (default, preserves tables and headings) or `pdf`
- `--output`, `-o` - Output file path (used with pdf format)
**Example:**
```bash
# Read as markdown (default, preserves tables and headings)
$SKILL_DIR/scripts/google-docs.py documents read 1abc...xyz
# Export as PDF
$SKILL_DIR/scripts/google-docs.py documents read 1abc...xyz --format pdf --output document.pdf
# Output as markdown:
# # Heading
#
# This is a paragraph.
#
# | Column 1 | Column 2 |
# |----------|----------|
# | Value 1 | Value 2 |
```
**Note:** Markdown and PDF export use Google's native Drive API export. Markdown preserves tables, headings, formatting, and structure with high fidelity. Both require the `drive.readonly` scope.
### documents import
Import a local markdown file as a natively formatted Google Doc. Uses Drive API HTML-to-Docs conversion for full markdown fidelity including tables, code blocks, headings, bold, italic, links, and lists.
```bash
$SKILL_DIR/scripts/google-docs.py documents import FILE_PATH [--title TITLE] [--document-id DOC_ID] [--folder-id ID]
```
**Arguments:**
- `file_path` - Local path to a markdown file
**Options:**
- `--title` - Document title (default: first H1 heading, or filename)
- `--document-id` - Existing document ID to update (replaces content)
- `--folder-id` - Parent folder ID for new documents
- `--no-format` - Skip post-import formatting
- `--json` - Output as JSON
**Examples:**
```bash
# Import a markdown file as a new Google Doc
$SKILL_DIR/scripts/google-docs.py documents import ./report.md --title "Monthly Report"
# Import using the first H1 heading as the title
$SKILL_DIR/scripts/google-docs.py documents import ./notes.md
# Update an existing document with new markdown content
$SKILL_DIR/scripts/google-docs.py documents import ./updated.md --document-id 1abc...xyz
# Import without post-import formatting
$SKILL_DIR/scripts/google-docs.py documents import ./raw.md --no-format
```
**Post-import formatting:** By default, the import applies 1.15x line spacing and 8pt space below paragraphs to the Normal text style. These can be overridden via frontmatter:
```yaml
---
title: My Document
line_spacing: 130
space_below: 10
---
```
After formatting, a readability summary is printed showing heading, paragraph, and list item counts.
**Note:** Requires `markdown`, `mdx-breakless-lists` Python libraries and the `drive.file` + `documents` scopes.
**See also:** For uploading files to Google Drive (non-markdown), sharing, organizing into folders, or exporting documents, use the **google-drive** skill.
### content append
Append text to the end of a document.
```bash
$SKILL_DIR/scripts/google-docs.py content append DOCUMENT_ID --text "Additional content"
```
**Arguments:**
- `document_id` - The Google Docs document ID
**Options:**
- `--text` - Text to append (required)
**Example:**
```bash
# Append text
$SKILL_DIR/scripts/google-docs.py content append 1abc...xyz --text "Meeting notes from today..."
# Output:
# ✓ Text appended successfully
```
### content insert
Insert text at a specific position in the document.
```bash
$SKILL_DIR/scripts/google-docs.py content insert DOCUMENT_ID --text "Insert this" --index 10
```
**Arguments:**
- `document_id` - The Google Docs document ID
**Options:**
- `--text` - Text to insert (required)
- `--index` - Position to insert at, 0-based (required)
**Example:**
```bash
# Insert text at the beginning (index 1, after title)
$SKILL_DIR/scripts/google-docs.py content insert 1abc...xyz --text "Introduction\n\n" --index 1
# Output:
# ✓ Text inserted successfully
```
**Note:** Index 0 is before the document content. Index 1 is at the beginning of content.
### content delete
Delete a range of content from the document.
```bash
$SKILL_DIR/scripts/google-docs.py content delete DOCUMENT_ID --start-index 10 --end-index 50
```
**Arguments:**
- `document_id` - The Google Docs document ID
**Options:**
- `--start-index` - Start position, inclusive (required)
- `--end-index` - End position, exclusive (required)
**Example:**
```bash
# Delete characters 10-50
$SKILL_DIR/scriRelated in Productivity
gitea-workflow
IncludedOrchestrate agile development workflows for Gitea repositories using the tea CLI. Use when working with Gitea-hosted repos and asking to 'run the workflow', 'continue working', 'what's next', 'complete the task cycle', 'start my day', 'end the sprint', 'implement the next task', or wanting guided step-by-step development assistance. Keywords: workflow, orchestrate, agile, task cycle, sprint, daily, implement, review, PR, standup, retrospective, gitea, tea.
microsoft-graph-gateway
IncludedRoute Microsoft Graph work in this workspace. Use when users want to read or write Outlook mail, calendar events, contacts, OneDrive or SharePoint files, Teams, Planner, To Do, users, groups, directory data, or arbitrary Microsoft Graph endpoints from VS Code. Prefer WorkIQ for common read scenarios. Use Microsoft Graph for write actions and gap-read scenarios that need exact Graph properties, filters, permissions, or endpoints.
copilotkit
IncludedUse when building with CopilotKit — setup, development, integrations, debugging, upgrading, or contributing. Routes to the appropriate specialized skill based on the task.
wordly-wisdom
IncludedProvides calibrated decision analysis using Charlie Munger-style multiple mental models, inversion, incentive mapping, circle-of-competence checks, misjudgment audits, second-order effects, and forecast updates. Use when the user asks for an oracle take, a hard call, a decision memo, a premortem, an outside view, a red-team, a sanity-check, what am I missing, think this through, or wants a strategy, hire, investment, plan, product, partnership, or major life choice analysed. Avoid for simple factual lookups or time-sensitive legal, medical, or market questions without fresh evidence.
swain-session
IncludedSession management and project status dashboard. Owns the full session lifecycle (start/work/close/resume), focus lane, bookmarks, worktree detection, and tab naming. Also serves as the project status dashboard — shows active epics, progress, actionable next steps, blocked items, tasks, GitHub issues, and recommendations. Worktree creation is deferred to swain-do task dispatch (SPEC-195). Triggers on: 'session', 'status', 'what's next', 'dashboard', 'overview', 'where are we', 'what should I work on', 'show me priorities', 'bookmark', 'focus on', 'session info'.
gandi
IncludedComprehensive Gandi domain registrar integration for domain and DNS management. Register and manage domains, create/update/delete DNS records (A, AAAA, CNAME, MX, TXT, SRV, and more), configure email forwarding and aliases, check SSL certificate status, create DNS snapshots for safe rollback, bulk update zone files, and monitor domain expiration. Supports multi-domain management, zone file import/export, and automated DNS backups. Includes both read-only and destructive operations with safety controls.