Build Docs Skill — Development skill for Claude Code
Claude Code skill that creates beautifully formatted Google Docs via the Docs API — auto-filed into the right Drive folder, consistently styled, and optionally shared.
How to install Build Docs Skill
This entry records only its repository, not the path inside it, so there is no
exact command to give. Open tenfoldmarc/build-docs-skill and copy the folder into
~/.claude/skills/, or the file into ~/.claude/agents/.
What Build Docs Skill does
Claude Code skill that creates beautifully formatted Google Docs via the Docs API — auto-filed into the right Drive folder, consistently styled, and optionally shared. Trigger with /build-docs.
Alternatives in Development
- Prompt Net Requests — I want to enhance the AsyncPlaywrightCrawlerStrategy to optionally capture network requests and console messag 85.8k ★
- /validate-output - Validate Generated Skills, Prompts, Agents, Or Hooks — Check that your generated output is properly formatted and ready to use 618 ★
- Module 18 Drive.En — Module 18 Lesson 4-4 — Assist Google Drive (drive_ops / gog drive) via prompts 347 ★
README
/build-docs — Claude Code Skill
A Claude Code skill that creates beautifully formatted Google Docs directly from the command line — auto-filed into the right Google Drive folder, consistently styled with your chosen theme, and optionally shared with collaborators.
What it does
Type `/build-docs` and Claude will:
- First run — guided setup — installs dependencies, walks you through Google OAuth, and lets you pick a formatting theme
- Ask which folder — lists your Google Drive folders and suggests the best match
- Ask what the doc is about — you describe it, Claude writes and structures the content
- Name it intelligently — e.g.
Client Name — Q2 Content Strategy - Create it via Google Docs API — fully formatted with your chosen theme, proper heading hierarchy, consistent typography
- Ask about sharing — optionally share with specific emails at any permission level
- Return the link — ready to open, send, or embed
Built-in Themes
Choose your theme on first install — saved automatically for all future docs:
1. Classic (Navy & Amber)
- Headings: Navy
#141B34, Accents: Amber#C05000 - Font: Georgia throughout
- Warm, professional, document-focused
2. Dark Pro (Charcoal & Blue)
- Headings: Charcoal
#1C1C1E, Accents: Electric Blue#0A84FF - Font: Georgia throughout
- Bold, modern, tech-forward
3. Clean Minimal (Black & White)
- Headings: Pure Black
#000000, Accents: Slate#4A4A4A - Font: Georgia throughout
- Maximum whitespace, editorial feel
Your theme is saved to `~/.claude/skills/build-docs/config.json` and used automatically on every future run. Reset it anytime by deleting that file.
Requirements
The skill handles all of this on first run — but here's what's needed:
- Python 3.8+
- pip packages:
google-auth google-auth-oauthlib google-auth-httplib2 google-api-python-client - Google Cloud project with Docs API and Drive API enabled
- OAuth 2.0 credentials (`client_secr
Related Skills
Send File
Upload a local file to the Google Drive mirror and share a link to it — optionally emailing that link to someo
Gdrive Push
Push this course's courseware (PPT + PDF, Learner Guide, Lesson Plan, assessments) to the user-provided Google
Tms Push
Update the course on lms-tms.tertiaryinfotech.com — set the Trainer Slides / Learner Slides / Learner Guide /
Google Workspace MCP
Multi-account MCP for Gmail, Calendar, Drive, Docs, and Sheets — 61 tools, token-efficient, macOS Keychain-bac
Brain Save
Save everything worth keeping from this conversation into the second brain vault, filed into the right domain
Auto Trigger
After any recon/probe step, route observed signals to the right tools and fire the auto-plan (Balanced policy)
Related Agents
Feature Crew Engineer Backend
Backend engineer. Implements plan.md steps for backend/infra code changes. Invoked during Build phase (and opt
Context
Gathers all context needed to onboard a dataset to Data Basis — raw source URLs, documentation, organization,
Play Release Notes
Generate Google Play "What's new" release notes from git history. Use when the user says "release notes", "wha