Plan Google Docs changes against the exact file, structure, revision, and access boundary, then verify content and delivery before calling the work done.
A Google Doc can look like one continuous page while the API sees tabs, segments, tables, headers, footnotes, objects, and UTF-16 indexes. That mismatch is where ordinary automation breaks: a range points at the wrong text, a collaborator changes the revision, a copied template keeps unexpected access, or a successful response gets mistaken for a verified result.
Google Docs Operations turns document work into a controlled sequence. It resolves the exact file and actor, inspects Drive metadata and live Docs structure, records placeholders and invariants, and chooses between a blank document, template copy, semantic replacement, or position-bound batch. Every write plan states its revision control, approval boundary, expected effect, read-back, and realistic recovery path.
Use it for creating, editing, templating, sharing, and exporting Google Docs through the Google Workspace CLI or the Docs and Drive APIs. It handles stale revisions, ambiguous timeouts, duplicate creates, changed placeholder counts, permission handoffs, and the gap between structural verification and visual review. It does not treat edit access as permission to share or publish, and it stops at a read-only plan when the target, authority, structure, or completion test is incomplete.
Version 1.0.0 was reviewed on 24 July 2026 and evaluated through Codex CLI with gpt-5.6-sol in 12 fresh read-only contexts. The candidate scored 100 across three cases, compared with 82.08 for the same agent without the skill and 85.83 for the exact free upstream. All cases passed. The smallest case-level margin over upstream was 10 points. The cases covered a template report with sharing and export boundaries, a stale UTF-16 positional edit, and the canonical blocked operation record. This evaluation measures the supplied cases; it does not prove that a live document is correct, that a connector has the claimed permissions, or that a write is safe without current read-back. The reviewed package SHA-256 is 1e332f45ed100af25dcecc0d7e5bb32e9b30556ca8870c511d26d3223cc8a27a.
The package includes a canonical operation-record contract and a read-only checker. Passing the checker confirms the record's shape, allowed methods, revision fields, required recovery notes, and verdict precedence. It cannot contact Google, inspect a live document, grant authority, or prove that a command ran. Maintenance and install support are handled by the platform-operated publisher for this listing.
Input
Plan a copy of template ID 1Template into folder 0Reports, replace the declared client, date, and summary tokens, export PDF, and share the result with one reviewer. Do not write yet.
Output
A revision-bound plan that separates Drive copy, Docs replacement, permission, and export operations; verifies the copied file, placeholder counts, ownership, access, content, and artifact; and keeps each mutation behind its own approval boundary.
Input
A reviewed batch used revision rev-17, but a collaborator inserted an emoji and a paragraph before the target. The requiredRevisionId write was rejected. Prepare the next safe step.
Output
Provide the exact document ID, requested outcome, authenticated actor, current access, tool surface, target tab or segment, revision and structure evidence, intended recipients or export format, and any content or access invariants. Ask for a read-only plan, an approval-ready operation record, execution of an already approved bounded change, verification of a completed operation, or recovery from an ambiguous or failed write.
Document ID and title, Google Docs MIME type, parent or shared-drive context, target tab or segment, and the requested deliverable.
An authenticated Google Workspace CLI, connector, or Docs and Drive API client with the least access needed for inspection and any explicitly approved operation.
Current revision, structural content, placeholder or anchor counts, capabilities, restrictions, relevant permissions, and collaborator or automation context.
The exact content, access, export, and notification actions allowed, the invariants to preserve, required read-backs, and a recovery path for material changes.
SKILL.md; controlled Google Docs inspection, planning, mutation, verification, sharing, export, and recovery workflow; canonical operation-record contract; read-only operation-record checker
No reviews yet.
A stopped write, fresh structural read, UTF-16-aware range recomputation, invariant comparison, renewed approval boundary, exact read-back, and no attempt to bypass the revision gate.
Input
Return the canonical JSON record for one planned batch update. The target and revision are known, mutation is not allowed yet, and owner approval is a critical blocker.
Output
Schema-valid JSON with exact target, authority, snapshot, revision-controlled operation, invariants, blocker, not-run execution and verification, handoff state, recovery action, and a blocked verdict accepted by the bundled checker.
Creator
Nnerlio
