From agentic-guardrails
Handling Google Docs/Sheets/Slides files that appear in a Google Drive for desktop synced folder as .gdoc/.gsheet/.gslides files. Use when a task involves one of these extensions or when the user asks to edit a Google Doc from their local Drive folder.
How this skill is triggered — by the user, by Claude, or both
Slash command
/agentic-guardrails:gdocs-bridgeThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
`.gdoc`, `.gsheet`, `.gslides` (and `.gdraw`, `.gform`, `.gmap`, `.gsite`)
.gdoc, .gsheet, .gslides (and .gdraw, .gform, .gmap, .gsite)
files in a Drive synced folder are not documents. Each is a tiny JSON stub
containing a URL and document ID. The real content lives only in Google's
editors.
.gdoc
corrupts the pointer; the hook denies this. Don't rename their extension
either.url / doc_id — that's the bridge.agw checkout flow on that file._workspace/ as usual.If you can see the doc's content (browser, screenshot, paste from the user) but have no export channel, you may rewrite it as markdown. This is transcription, not export — it is lossy and can silently truncate, so:
<name>.transcribed.md in _workspace/, never as a file that
looks like the original.Report.gdoc with Report.docx in the synced folder does not
update the Google Doc — it creates a second, unrelated file in Drive.npx claudepluginhub profsynapse/agentic-guardrails-plugin --plugin agentic-guardrailsGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.