md-to-gdoc

What This Skill Does

The md-to-gdoc skill serves as a seamless bridge between local markdown-based documentation and the Google Workspace ecosystem. By leveraging the specialized gog CLI tool, this skill automates the conversion of .md files into fully formatted Google Docs. Unlike simple text pasting, this process interprets markdown syntax—such as headers, blockquotes, code blocks, and tables—and maps them to native Google Docs styles (e.g., Heading 1–6, Courier New for code blocks). This ensures that your research notes, technical specifications, or project drafts maintain their structural integrity while becoming collaborative documents for team sharing.

Installation

To integrate this skill into your environment, use the OpenClaw CLI within your terminal: clawhub install openclaw/skills/skills/brennerspear/md-to-gdoc Ensure you have the gog tool installed and authenticated by running gog auth add <email> before execution. The skill also requires python3 to handle the underlying JSON parsing used in the conversion scripts.

Use Cases

• Documentation Export: Convert local technical project notes into professional documentation for stakeholders who prefer Google Docs.
• Research Aggregation: Take a folder of markdown-based research and generate a single, polished Google Doc for team review.
• Content Workflow: Draft articles or blog posts in a distraction-free markdown environment and instantly push them to a shared Google Drive folder for editorial collaboration.

Example Prompts

1. "Convert my notes.md file into a Google Doc and title it 'Q4 Project Plan'."
2. "Take the markdown file at ./specs/api-guide.md and upload it to the Google Drive folder with ID 1abc123456789."
3. "I have a markdown document here; please push it to Google Docs using my work email account."

Tips & Limitations

• Heading Importance: The converter relies strictly on # syntax. If your file does not contain valid markdown headers, the output will appear as plain body text. Always verify your headers before running.
• Deterministic Process: The skill uses a two-step approach: creating an empty document first, then populating it via the update command. This ensures the API correctly applies formatting styles.
• Italic Limitation: Currently, the gog CLI parser may struggle with *italic* markdown syntax. It is recommended to use bold or headers instead if strict formatting is required.
• Lists: Note that lists will appear with manual characters (e.g., bullet dots) rather than native Google Docs dynamic list objects.