Recipe Create Doc From Template

Copy a Google Docs template, fill in content, and share with collaborators.

Security Scan

The skill's requests and instructions are consistent with its stated purpose (copy a Google Docs template, populate it, and share it); it delegates Google access to the gws CLI / gws-* skills and does not ask for unrelated secrets or install arbitrary code.

Purpose & Capability

The name/description match the actions in SKILL.md: copying a Drive file, writing to a Docs document, and creating Drive permissions. Requiring the gws CLI and the gws-drive/gws-docs helper skills is coherent for this functionality.

Instruction Scope

The instructions explicitly run gws CLI commands that will access Drive and Docs and create sharing permissions — this is expected. However, the recipe contains hardcoded example placeholders (TEMPLATE_DOC_ID, NEW_DOC_ID) and an example email ([e-mail]); if used as-is the agent could attempt to share documents without further confirmation. The SKILL.md does not require or document a confirmation step before sharing.

Install Mechanism

There is no install spec and no code files; this is an instruction-only recipe that calls an existing CLI (gws). That is the lowest-risk install profile.

Credentials

The skill itself requests no environment variables or credentials. It depends on gws and the gws-drive/gws-docs skills, which are the expected places to handle OAuth/credentials for Google Workspace; this delegation is proportionate. Users should be aware those other skills will require Google credentials.

Persistence & Privilege

always is false and there is no persistent installation or modification of other skills. The skill does instruct operations that modify Drive/Docs state (copying and sharing) but does not request elevated platform privileges.

Assessment

This recipe appears to do what it says: it runs the gws CLI to copy a Docs template, add text, and grant permissions. Before installing/using it: (1) ensure the gws CLI on your agent is the one you expect and authenticated to the correct Google account; (2) replace TEMPLATE_DOC_ID and NEW_DOC_ID placeholders and the example email with the intended values; (3) consider adding an explicit confirmation step before the recipe runs the permissions/create command to avoid accidental sharing; and (4) review and understand the gws-drive and gws-docs skills because those will manage OAuth tokens and are the components that actually hold Google credentials.

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": "[e-mail]"}'`