gdocs-markdown
Create Google Docs from Markdown files. Use when the user wants to create a Google Doc from Markdown content, or when working with gog CLI and need to populate Google Docs with content. This skill handles the conversion Markdown → DOCX → Google Docs via Drive upload, since gog docs CLI only supports create/export/cat/copy but NOT write/update content.
Why use this skill?
Easily convert and upload your Markdown files to Google Docs with the gdocs-markdown OpenClaw skill. Simplify your documentation workflow today.
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/techlaai/gdocs-markdownWhat This Skill Does
The gdocs-markdown skill serves as a vital bridge between local Markdown-based documentation workflows and the Google Docs ecosystem. Because the standard 'gog' CLI tool lacks native functionality for writing or updating content within existing Google Docs, this skill provides a robust automated workflow to overcome that limitation. It operates by converting Markdown files into DOCX format using Pandoc, then utilizing the Google Drive API to upload the file, which automatically triggers a conversion into a fully editable Google Doc. This allows users to maintain their 'docs-as-code' practice while satisfying requirements for collaborative Google Docs documents.
Installation
To install this skill, run the following command in your terminal: clawhub install openclaw/skills/skills/techlaai/gdocs-markdown. Once installed, it is critical to ensure the helper script has the correct execution permissions to operate within your workspace. Navigate to the installation directory and run: chmod +x ~/.openclaw/workspace/skills/gdocs-markdown/scripts/gdocs-create.sh. The system is designed to automatically handle the retrieval of the Pandoc binary during its first execution, ensuring that dependencies are managed with minimal user intervention.
Use Cases
This skill is ideal for technical writers, developers, and project managers who prefer authoring in Markdown but must deliver professional reports or specifications in Google Docs. It is perfect for generating status reports from code-based notes, creating documentation that needs to be shared with non-technical stakeholders, and automating the conversion of README files into branded Google Docs. It simplifies the transition from local drafting to cloud-based collaboration.
Example Prompts
- "Use the gdocs-markdown skill to convert my local report.md file into a Google Doc titled 'Quarterly Technical Review'."
- "I need to publish our project documentation from the /docs/specs.md file to a new Google Doc; please handle the conversion and provide me the edit link."
- "Convert my latest markdown meeting notes located at /tmp/notes.md into a shared Google Doc document."
Tips & Limitations
When using this skill, keep in mind that Google Drive triggers a conversion process during the upload. While the resulting document is fully editable, complex Markdown elements or specific custom CSS may require minor formatting adjustments once inside the Google Docs editor. The original DOCX file will be stored in your Drive; you may want to clean this up periodically to save space. Always verify your 'gog' CLI authentication status before running the command to ensure the upload process completes successfully.
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-techlaai-gdocs-markdown": {
"enabled": true,
"auto_update": true
}
}
}Tags(AI)
Flags: file-read, file-write, external-api, code-execution