setup-provider-google-drive

Set up Google Drive provider scaffolding in adapter repositories.

Updated Feb 28, 2026
One-click install
npx skills add https://github.com/tachiiri-org/agent-ops --skill setup-provider-google-drive
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup-provider-google-drive
Source: https://github.com/tachiiri-org/agent-ops/tree/main/.codex/skills/setup-provider-google-drive
Command: npx skills add https://github.com/tachiiri-org/agent-ops --skill setup-provider-google-drive

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the setup process for adapter repositories that directly integrate with Google Drive, ensuring correct scaffolding and adherence to best practices.

Core Features & Use Cases

  • Provider Scaffolding: Adds minimal, necessary Google Drive-specific placeholders and structure.
  • Boundary Verification: Ensures the repository's integration point is indeed with Google Drive.
  • Use Case: When starting a new project that needs to interact with Google Drive as an adapter, this Skill provides the foundational setup, saving time and preventing common integration errors.

Quick Start

Run the setup-provider-google-drive command to add Google Drive scaffolding to the current repository.

Frequently Asked Questions about setup-provider-google-drive

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

FAQPage Schema
How do I set up Google Drive provider scaffolding for an adapter repository?

To set up Google Drive provider scaffolding, run the setup command to add minimal required placeholders and verify direct integration. This guides the process by referencing provider-specific documentation and general principles for roles and domains.

What is the best way to start integrating a new adapter with Google Drive?

The best way to start a Google Drive integration is to use a scaffolding setup command that adds minimal necessary placeholders. This provides the foundational structure, saving time and preventing common integration errors from the start.

When do I need to verify direct integration for a Google Drive adapter?

You need to verify direct integration for a Google Drive adapter before adding scaffolding to ensure the repository's integration point is indeed with Google Drive. This boundary verification prevents incorrect provider configurations.

Does this Google Drive integration setup require additional dependencies?

No, this Google Drive integration setup does not require additional dependencies. It adds minimal required placeholders and guides the setup process by referencing provider-specific documentation and general principles for roles and domains.

Why does my Google Drive adapter setup need provider-specific documentation?

Your Google Drive adapter setup needs provider-specific documentation to correctly guide the scaffolding process and adhere to best practices. Referencing this documentation ensures correct roles and domains configuration for the integration.