Skill

repo-to-gdrive

Upload a generated document (PDF, markdown, etc.) to Google Drive via the configured Google Workspace MCP server (gws-personal by default, gws-dsrholdings or other overridable). Use when the user says "upload this PDF to Drive", "send this doc to Google Drive", "put this in my Drive folder", or after generating a document and wanting to distribute it via Google Drive.

npx claudepluginhub danielrosehill/claude-code-plugins --plugin repo-to-content

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Upload a single file to Google Drive via an MCP tool.

SKILL.md

Similar Skills

angular-new-app

100.1k

Creates new Angular apps using Angular CLI with flags for routing, SSR, SCSS, prefixes, and AI config. Follows best practices for modern TypeScript/Angular development. Use when starting Angular projects.

angular-angular-1

context7-cli

53.8k

Executes ctx7 CLI to fetch up-to-date library documentation, manage AI coding skills (install/search/generate/remove/suggest), and configure Context7 MCP. Useful for current API refs, skill handling, or agent setup.

3 files

upstash-context7-1

Stats

Stars0

Forks0

Last CommitApr 19, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

repo-to-gdrive

Upload a single file to Google Drive via an MCP tool.

Inputs

file (required): absolute path to the file to upload.

folder_id (optional): target Drive folder ID. Resolution order:

Explicit folder_id arg
Per-index-repo gdrive_folder_id (if invoked after repo-to-docs-index)
Config gdrive_default_folder_id
Prompt the user

name (optional): name to use on Drive. Defaults to local filename.

mcp_server (optional): MCP server key (default: config gdrive_mcp_server, itself defaulting to gws-personal).

Procedure

Load config from ~/.config/repo-to-docs/config.json.

Resolve MCP server: prefer mcp_server arg, then config.gdrive_mcp_server, then "gws-personal".

Resolve folder_id via the order above. If prompting, show the user the available configured folders.

Invoke the appropriate MCP upload tool. The expected tool name pattern is <mcp_server>__upload_file (common variants: gws-personal, gws-dsrholdings). Typical arguments:

file_path: absolute path to the local file
folder_id: Drive folder ID
name: optional target filename

On success, report:

Drive file ID
Drive web link (if returned)
Target folder (ID + name if the MCP resolves it)

On failure, surface the MCP error message and suggest verifying the MCP server is enabled (claude mcp list).

Notes

The plugin does not implement Drive auth itself — it relies on whatever GWS MCP server the user has configured.

This skill never modifies the source file or generates content — it's a thin upload wrapper.

repo-to-gdrive

Upload a single file to Google Drive via an MCP tool.

Inputs

file (required): absolute path to the file to upload.
folder_id (optional): target Drive folder ID. Resolution order:
1. Explicit folder_id arg
2. Per-index-repo gdrive_folder_id (if invoked after repo-to-docs-index)
3. Config gdrive_default_folder_id
4. Prompt the user
name (optional): name to use on Drive. Defaults to local filename.
mcp_server (optional): MCP server key (default: config gdrive_mcp_server, itself defaulting to gws-personal).

Procedure

Load config from ~/.config/repo-to-docs/config.json.
Resolve MCP server: prefer mcp_server arg, then config.gdrive_mcp_server, then "gws-personal".
Resolve folder_id via the order above. If prompting, show the user the available configured folders.
Invoke the appropriate MCP upload tool. The expected tool name pattern is <mcp_server>__upload_file (common variants: gws-personal, gws-dsrholdings). Typical arguments:
- file_path: absolute path to the local file
- folder_id: Drive folder ID
- name: optional target filename
On success, report:
- Drive file ID
- Drive web link (if returned)
- Target folder (ID + name if the MCP resolves it)
On failure, surface the MCP error message and suggest verifying the MCP server is enabled (claude mcp list).

Notes

The plugin does not implement Drive auth itself — it relies on whatever GWS MCP server the user has configured.
This skill never modifies the source file or generates content — it's a thin upload wrapper.