Google Docs from 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.

Security Scan

The skill's stated purpose (convert Markdown → Google Docs via gog and pandoc) is plausible, but the package omits declaring required binaries and relies on an undocumented runtime download (pandoc), creating an incoherence and a runtime download risk you should review before installing.

Purpose & Capability

The SKILL.md clearly requires the gog CLI to be authenticated and pandoc to perform the conversion, but the registry metadata lists no required binaries or primary credential. That mismatch (declaring no required binaries while the workflow requires gog and pandoc) is an inconsistency — the skill should declare these dependencies.

Instruction Scope

The instructions themselves stay on‑topic (convert Markdown → DOCX → upload to Drive). However they instruct an 'auto-download' of pandoc to /tmp on first use. Auto-downloading an executable at runtime expands the scope (network fetch, write to /tmp, execute) beyond simple file conversion and isn't documented in the registry metadata.

Install Mechanism

There is no formal install spec, but the skill's runtime behavior includes auto-downloading a pandoc binary to /tmp. Runtime downloads of executables are higher risk unless the source is explicit and trusted; the SKILL.md does not specify the exact download URL or verification steps. The presence of a helper script that performs these actions increases the need to review it.

Credentials

The skill requests no environment variables or credentials in metadata, which is good. It does rely on an already-authenticated gog CLI (i.e., the user's Google credentials via gog) but does not declare that requirement in the registry fields — this is a minor proportionality/documentation issue rather than an extra privilege demand.

Persistence & Privilege

The skill is not marked always:true and has no special persistence flags. Model invocation is not disabled, so the agent could call the skill. Given the script may perform network downloads and execute a binary, allowing autonomous invocation increases risk; consider requiring explicit user invocation or disabling autonomous invocation if you want to avoid unexpected downloads.

What to consider before installing

Before installing: (1) Review the scripts/gdocs-create.sh contents to see exactly what it downloads and from where — verify the pandoc download URL is an official release (e.g., GitHub releases) and that the script verifies checksums. (2) Ensure you are comfortable with the script writing to /tmp and executing a downloaded binary. (3) Confirm you have the gog CLI installed and authenticated to the intended Google account; the skill will use that existing authentication to upload files. (4) If you want to reduce risk, run the script manually in a sandbox or container first, or modify it to use a system-installed pandoc rather than auto-downloading. Providing the script's full content or the pandoc download URL would allow a higher-confidence assessment.

Create Google Docs from Markdown files using the workflow: Markdown → DOCX → Drive Upload → Google Docs.

Why This Skill Exists

gog docs CLI does NOT support writing/updating content to Google Docs. It only supports:

• create - Create empty doc
• export - Export to file
• cat - Read content
• copy - Copy existing doc

This skill provides the missing workflow to create Google Docs WITH content from Markdown.

Author

Created by techla

Prerequisites

• gog CLI authenticated with Google account
• pandoc binary (auto-downloaded on first use if not available)

Installation Note

After installing from ClawHub, fix the script permissions:

chmod +x ~/.openclaw/workspace/skills/gdocs-markdown/scripts/gdocs-create.sh

Usage

Quick Create

# Create Google Doc from markdown file
gdocs-create.sh /path/to/file.md "Tiêu đề Document"

Manual Workflow

If you need more control, follow these steps:

1. Ensure pandoc is available:

   # Auto-downloaded to /tmp/pandoc-3.1.11/bin/pandoc on first use
   # Or use system pandoc if available
   

2. Convert Markdown to DOCX:

   /tmp/pandoc-3.1.11/bin/pandoc input.md -o output.docx
   

3. Upload to Drive (auto-converts to Google Docs):

   gog drive upload output.docx
   

4. Result: Google Drive returns a link to the converted Google Doc

Script Reference

See scripts/gdocs-create.sh for the helper script that automates this workflow.

Example

# Create a report from markdown
echo "# Báo Cáo\n\nNội dung..." > /tmp/report.md
gdocs-create.sh /tmp/report.md "Báo Cáo Tháng 2"

# Output: https://docs.google.com/document/d/xxxxx/edit

Notes

• Google Drive automatically converts DOCX to Google Docs format on upload
• The resulting document is fully editable in Google Docs
• Original DOCX file remains in Drive but can be deleted if only Google Docs version is needed