Persona Content Creator
Operate as a Workspace-backed content creator persona—draft in Docs, store in Drive, announce in Chat, and email reviews via Gmail and Slides workflows.
Overview
persona-content-creator is an agent skill most often used in Grow (also Launch distribution) that orchestrates Google Workspace CLI skills to create, organize, and distribute content.
Install
npx skills add https://github.com/googleworkspace/cli --skill persona-content-creatorWhat is this skill?
- Persona bundles 5 utility skills: gws-docs, gws-drive, gws-gmail, gws-chat, gws-slides
- Draft and update copy with `gws docs +write` including Docs API formatting
- Browse folders with `gws drive files list` and upload media via `gws drive +upload`
- Announce finished files using `gws workflow +file-announce` in Chat
- Send review requests with `gws gmail +send`; track schedules in a shared Content Calendar Sheet
- 5 prerequisite utility skills listed in persona metadata
- OpenClaw persona metadata version 0.22.5
Adoption & trust: 15.8k installs on skills.sh; 26.9k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You publish from Docs and Drive but your agent treats Gmail, Chat, and Slides as separate one-offs with no shared content-creation playbook.
Who is it for?
Solo creators and indie founders already on `gws` who want a single persona for blogs, launch posts, and internal content ops.
Skip if: Teams not on Google Workspace, purely static-site-only publishers, or builders who only need one-off Doc edits without distribution.
When should I use this skill?
Create, organize, and distribute content across Workspace.
What do I get? / Deliverables
Your agent runs a consistent Workspace content workflow—draft, store, announce, and request review—using the bundled gws utility skills.
- Drafted Docs content and organized Drive asset folders
- Chat announcements and email review requests for published pieces
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Ongoing content creation and calendar management sit on Grow as the primary shelf, even though distribution touches Launch. The persona’s core loop is drafting and organizing content assets, which is the content subphase; Chat announce and email are distribution edges.
Where it fits
Draft a weekly newsletter section in Docs and file images in a dated Drive folder before publish.
After upload, run file-announce in Chat so the launch thread sees the final PDF or slide deck.
Prepare product changelog copy in Docs while the app branch is still in Build.
How it compares
A persona workflow across multiple gws skills—not a single Docs or SEO automation skill.
Common Questions / FAQ
Who is persona-content-creator for?
Indie builders and small marketing stacks that standardize on Google Workspace and the `gws` CLI for day-to-day content production.
When should I use persona-content-creator?
Use it in Grow (content) for drafting and asset organization, Launch (distribution) when announcing shipped posts, and Build (docs) when preparing launch copy in Docs.
Is persona-content-creator safe to install?
It chains mail, chat, and drive APIs; review OAuth scopes, shared folder permissions, and the Security Audits panel on this page before automating sends.
SKILL.md
READMESKILL.md - Persona Content Creator
# Content Creator > **PREREQUISITE:** Load the following utility skills to operate as this persona: `gws-docs`, `gws-drive`, `gws-gmail`, `gws-chat`, `gws-slides` Create, organize, and distribute content across Workspace. ## Relevant Workflows - `gws workflow +file-announce` ## Instructions - Draft content in Google Docs with `gws docs +write`. - Organize content assets in Drive folders — use `gws drive files list` to browse. - Share finished content by announcing in Chat with `gws workflow +file-announce`. - Send content review requests via email with `gws gmail +send`. - Upload media assets to Drive with `gws drive +upload`. ## Tips - Use `gws docs +write` for quick content updates — it handles the Docs API formatting. - Keep a 'Content Calendar' in a shared Sheet for tracking publication schedules. - Use `--format yaml` for human-readable output when debugging API responses.