Recipe Create Doc From Template
Spin up a shared Google Doc from a template and fill a project brief without clicking through Drive manually.
Overview
recipe-create-doc-from-template is an agent skill for the Build phase that copies a Google Docs template, fills content via gws, and shares the new doc with collaborators.
Install
npx skills add https://github.com/googleworkspace/cli --skill recipe-create-doc-from-templateWhat is this skill?
- 4-step recipe: copy template via gws drive, write body via gws docs, grant writer permissions
- Hard prerequisite: load gws-drive and gws-docs skills before running commands
- Uses gws CLI with JSON payloads for copy, +write text injection, and permissions create
- Names the new file (e.g. Project Brief - Q2 Launch) while preserving template structure
- Shares the new doc to a teammate email with writer role in one command
- 2 prerequisite skills (gws-drive, gws-docs)
Adoption & trust: 15.9k installs on skills.sh; 26.9k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You need a fresh Google Doc from a company template with real content and team write access, but doing it by hand in Drive breaks your agent flow.
Who is it for?
Builders on gws who repeatedly produce briefs or launch docs from the same template and want copy-paste-safe CLI steps.
Skip if: Teams without gws installed, without template file IDs, or who only need read-only exports instead of collaborative Docs.
When should I use this skill?
You need to copy a Google Docs template, inject content, and share with collaborators via gws after gws-drive and gws-docs are loaded.
What do I get? / Deliverables
You get a new document ID, populated sections, and writer permissions for your team—ready to extend or hand to the next planning skill.
- New Google Doc with chosen title
- Populated markdown-style sections
- Writer permission for specified email
Recommended Skills
Journey fit
Canonical shelf is Build/docs because the recipe’s output is a living document collaborators edit during product work. It automates doc creation, templated copy, and writer sharing—the core docs workflow for solo builders shipping specs and briefs.
How it compares
Use this structured recipe instead of one-off Chat prompts that cannot reliably run Drive copy, Docs write, and permissions APIs in order.
Common Questions / FAQ
Who is recipe-create-doc-from-template for?
Solo and indie builders using OpenClaw or Claude Code with the gws CLI who document projects in Google Docs and already rely on gws-drive and gws-docs.
When should I use recipe-create-doc-from-template?
Use it during Build/docs when you have a template ID and need a named doc with objectives and shared writers; also when validating scope artifacts that live in Docs before full implementation.
Is recipe-create-doc-from-template safe to install?
It runs shell commands against Google APIs and can change file sharing; review the Security Audits panel on this page and confirm OAuth scopes and collaborator emails before granting writer access.
SKILL.md
READMESKILL.md - Recipe Create Doc From Template
# Create a Google Doc from a Template > **PREREQUISITE:** Load the following skills to execute this recipe: `gws-drive`, `gws-docs` Copy a Google Docs template, fill in content, and share with collaborators. ## Steps 1. Copy the template: `gws drive files copy --params '{"fileId": "TEMPLATE_DOC_ID"}' --json '{"name": "Project Brief - Q2 Launch"}'` 2. Get the new doc ID from the response 3. Add content: `gws docs +write --document-id NEW_DOC_ID --text '## Project: Q2 Launch ### Objective Launch the new feature by end of Q2.'` 4. Share with team: `gws drive permissions create --params '{"fileId": "NEW_DOC_ID"}' --json '{"role": "writer", "type": "user", "emailAddress": "team@company.com"}'`