public-google-drive

Public Google Drive is an agent skill designed to enable LLM coding agents to create and edit Google Docs and Sheets hosted on Memyard without requiring a Google account login. Documents can be viewed via a shareable link, and registration is automatic on first use.

Purpose

This skill is mainly used to allow AI coding agents to programmatically generate and modify Google Docs and Sheets without requiring manual login to a Google account. All documents are stored in Memyard's Google Workspace, not in the user's personal Google Drive.

Main Capabilities

• Create new Google Docs or Sheets in Memyard's workspace.
• Append or insert text into documents you created, or append rows to spreadsheets you created.
• View documents via a public link (for example, https://app.memyard.com/share/<id> ). Anyone with the link can view it, but only the creator (that is, the corresponding agent) can edit it.
• List and retrieve metadata for your own documents (no paid plan required).

How to Use

Copy the repository into the agent's skills folder, then restart or start a new session. When creating or editing a document through Public Google Drive for the first time, the tool automatically registers and stores credentials in <HOME>/.memyard/agent_config.json(where <HOME> on macOS/Linux is $HOME, and on Windows is %USERPROFILE%). The same credentials are reused afterward, with no separate "registration" step and no need to copy a URL or key.

Write operations use a two-step "plan first, then execute" process so the server can check scope, size, and content before writing:

1. Plan (propose): Tell the server what you want to do (create a document/spreadsheet, or append/insert content into an existing document), along with a brief content summary (for example, "meeting notes and action items"). Do not send the full content at this stage. The server returns either approval (including a plan ID and a short validity window, for example 10 minutes, as well as constraints such as maximum characters or rows) or rejection (including the reason and optional adjusted constraints). If rejected, do not call execute; instead, revise the proposal or content and retry planning.
2. Execute (write): Send the plan ID and the actual payload (title, content, rows, etc.). The server performs the write and returns the result (such as resource ID and view URL). Each plan ID can be used only once; to write again, you need to obtain a new plan.

The complete request/response format and examples are in SKILL.md.

Applicable Scenarios

Suitable for scenarios where an AI coding agent needs to automatically generate or update Google Docs/Sheets, such as automatically generating meeting notes, reports, data tables, etc., and where logging in with a Google account is not desired or not possible.

Limitations

• Documents are stored in Memyard's Google Workspace, not in a personal Drive.
• Only the creator (agent) can edit; others can only view via the link.
• Write operations are subject to plan constraints (such as maximum characters or rows), and the plan ID is valid only once.
• There are rate limits (such as registrations per IP, and creations/writes per agent per hour); when triggered, a 429 is returned with a retry time.
• If a plan is rejected, revise it and plan again; if a plan expires or is invalid (400), obtain a new plan and execute within the time window.

This skill uses the MIT license; see LICENSE for details.