Help us improve
Share bugs, ideas, or general feedback.
From google-drive
Documents-first net-new Google Docs creation plus connector-first Google Docs editing in local Codex plugin sessions, with target-document checks, connector-readback verification, and reference routing for formatting, citations, tables, and write-safety.
npx claudepluginhub robinebers/converted-plugins --plugin google-driveHow this skill is triggered — by the user, by Claude, or both
Slash command
/google-drive:google-docsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use this skill for Google Docs work in Codex local-plugin sessions where Browser Use and rendered visual inspection are unavailable.
assets/google-docs-small.svgassets/google-docs.pngreferences/reference-citations-and-hyperlinks.mdreferences/reference-connector-runtime-and-safety.mdreferences/reference-figures-and-image-insertion.mdreferences/reference-foreground-guard.mdreferences/reference-headings-and-question-format.mdreferences/reference-import-docx-to-native-docs.mdreferences/reference-request-shapes-and-write-safety.mdreferences/reference-response-and-list-format.mdreferences/reference-section-completeness-and-final-pass.mdreferences/reference-table-formatting-deep-dive.mdMandates invoking relevant skills via tools before any response in coding sessions. Covers access, priorities, and adaptations for Claude Code, Copilot CLI, Gemini CLI.
Share bugs, ideas, or general feedback.
Use this skill for Google Docs work in Codex local-plugin sessions where Browser Use and rendered visual inspection are unavailable.
Net-new Google Doc deliverables must be authored through [@documents](plugin://documents@openai-primary-runtime) as local .docx files first, then uploaded as native Google Docs.
This file is intentionally minimal and only covers:
All formatting, citation, table, and production rules live in references/.
Latency is not a constraint for this skill, so always read the relevant reference files before performing the task.
Use this routing:
[@documents](plugin://documents@openai-primary-runtime) to create a local .docx first, including that skill's DOCX QA workflow..docx into Drive as a native Google Docs document. Read references/reference-import-docx-to-native-docs.md.Do not reference the local .docx in the final answer after successful native import. The final answer includes the Google Docs link only.
This plugin is for the local Codex plugin environment.
Maintain working state for the active document task instead of re-deriving context from scratch after every step.
Keep the target URL, document id, tabId, source materials, resolved sections or tables, live indexes, write batches, and verification status current as the task progresses.
Refresh that state before connector writes when source gathering, document switches, connector errors, or runtime resets could make it stale.
Inserted or edited content must match the surrounding document's existing structure and connector-observable presentation closely enough that it should read as native template content. This is launch-blocking, not cosmetic. Treat missing section hierarchy, mismatched heading level, font family, font size, bolding, link coverage, table styling, or template-shape drift visible in connector data as a failed output that must be corrected before handoff. Do not claim rendered visual verification when the model cannot see the document.
For presentation-oriented documents, structural completeness is not enough. A document can have all requested sections, headings, tables, and placeholders resolved while still being too dense, monotonous, or hard to scan. Treat readability, hierarchy, and appropriate use of visual devices as part of completion, not as optional polish.
Prefer one simple proven workflow over a large tree of recovery branches. When a task matches a known successful pattern, follow that pattern directly instead of re-evaluating every possible insertion or fallback path. Do not let accumulated edge-case guardrails turn a straightforward document task into a long blocker-analysis exercise. For net-new Google Doc deliverables, follow Default Routing first. For existing document editing tasks and follow-on edits after a DOCX import, prefer this general sequence when viable:
For any secondary element that cannot be verified through connector reads, either use a connector-supported path with readback or clearly state the verification limit.
If a simple verified workflow is viable, use it. Do not drift into speculative alternate paths.
Before final handoff, explicitly verify these with connector readback:
text/html through Google Drive and use the generated markup/CSS as a rendered-structure proxy for heading tags, font families, font sizes, table cells, fills, widths, and paragraph orderingIf any check fails, the task is not complete. If a simple known-good workflow is available and the run instead collapses into repeated fallback experiments, the task is also not complete.
Before any content write or edit operation:
If Default Routing uses [@documents](plugin://documents@openai-primary-runtime):
[@documents](plugin://documents@openai-primary-runtime) plugin skill.references/reference-import-docx-to-native-docs.md.If Default Routing uses connector edit workflow:
references/reference-connector-runtime-and-safety.md.references/reference-foreground-guard.md for target-document identity checks.references/reference-request-shapes-and-write-safety.md.references/.Do not execute content edits until the required references are read in the current turn.
tabId.references/reference-foreground-guard.md and re-confirm the target document id, URL, and tabId when applicable.get_document_text when paragraph text and indexes are enoughget_document when full structure, styles, tabs, or non-text elements matterfind_document_text_range when exact source text can anchor the target rangeget_paragraph_range or get_document_paragraph_range when an index must expand to paragraph boundariesget_tables before editing or rebuilding table contenttabId and carry it through all reads and writes.| Task area | Required reference file |
|---|---|
| Runtime attachment, section targeting, safety, and recovery | references/reference-connector-runtime-and-safety.md |
Importing a locally created .docx into native Google Docs | references/reference-import-docx-to-native-docs.md |
| Confirming the target Google Doc before every write batch | references/reference-foreground-guard.md |
| Request objects, tab-aware calls, range-safe writes, sampling the local style baseline, and connector-readback verification when style metadata is incomplete | references/reference-request-shapes-and-write-safety.md |
| Header and prompt structure, including bolding the question being answered and matching local heading/body typography | references/reference-headings-and-question-format.md |
| Response structure, list behavior, and one-idea-per-bullet formatting | references/reference-response-and-list-format.md |
| Citation formatting and hyperlink requirements | references/reference-citations-and-hyperlinks.md |
| Native table creation, local table-style matching, population, styling, and acceptance checks | references/reference-table-formatting-deep-dive.md |
| Figures, diagrams, image preparation, insertion, and figure-block placement | references/reference-figures-and-image-insertion.md |
| Section completeness, source-list formatting, typography consistency, connector-observable comparison, and final production pass | references/reference-section-completeness-and-final-pass.md |