shimmy-tool-gdrive

Guide Google Drive MCP Shimmy tool use and maintenance with versioned context.

2|Updated Feb 14, 2026
One-click install
npx skills add https://github.com/wadebee/shimmy --skill shimmy-tool-gdrive
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shimmy-tool-gdrive
Source: https://github.com/wadebee/shimmy/tree/main/tools/gdrive/agent
Command: npx skills add https://github.com/wadebee/shimmy --skill shimmy-tool-gdrive

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you use and maintain the context-first Google Drive MCP Shimmy tool without having to rediscover the repository structure, version-specific guidance, or OAuth setup details each time.

Core Features & Use Cases

  • Tool-specific operating guidance: Follow the canonical workflow for the Google Drive MCP tool from the skill entry point.
  • Context-aware maintenance: Keep repository, tool, and version instructions aligned when updating the concrete runtime.
  • OAuth and local build handling: Work with the required credential inputs and preserve the local image build behavior for reliable execution.
  • Use case: Update or operate the Google Drive integration while ensuring the correct repository context and versioned instructions are consulted.

Quick Start

Use this skill to follow the Google Drive MCP workflow and apply the context and version instructions before making changes or running the tool.

Frequently Asked Questions about shimmy-tool-gdrive

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

FAQPage Schema
How do I set up OAuth credentials for a Google Drive MCP tool?

To operate the Google Drive MCP tool, follow the canonical workflow from the skill entry point and apply context-first repository instructions before running or updating the integration.

How do I update my Google Drive MCP runtime without breaking repository context?

To update the Google Drive MCP runtime, keep repository, tool, and version instructions aligned by consulting the context-aware maintenance guidance before making changes to the concrete runtime.

What is context-first tooling for Google Drive MCP?

Context-first tooling for Google Drive MCP is an approach that reads repository structure and version-specific guidance before executing tasks, preventing the need to rediscover setup details each time.

Do I need local build behavior to run Google Drive MCP tools?

Yes, preserving local build behavior is required for reliable execution. The workflow ensures the local image build behavior is maintained alongside OAuth credential validation during runtime operations.

Why does my Google Drive MCP tool lose its version guidance after an update?

Version guidance is lost when repository, tool, and version instructions fall out of alignment. The tool requires context-aware maintenance to keep versioned instructions synced with the concrete runtime.