π³ Content Creator Persona (gws CLI)
Operate as a content creator across Docs, Drive, Gmail, Chat and Slides
- What
- Operate as a content creator across Docs, Drive, Gmail, Chat and Slides
- Cost
- Free
- Needs
- a paid Google Workspace account; the gws CLI installed and authenticated; this persona also requires the gws-docs, gws-drive, gws-gmail, gws-chat and gws-slides utility skills loaded
- Install
- Copy the installer prompt below into your Muse β your agent does the rest.
π³ Requires a paid Google Workspace account for the gws CLI β no free tier. Curated by Skill Harbor β an agent persona for content work in Workspace: draft in Docs (`gws docs +write`), organize assets in Drive folders, announce finished pieces in Chat (`gws workflow +file-announce`), send review requests by email, and upload media to Drive, with practical tips like keeping a shared Content Calendar Sheet. Distinct from the sibling personas exec-assistant and researcher (lot 31): those cover executive assistance and research workflows; this one is purely about creating, organizing and distributing content. By @googleworkspace, listed here with credit to its creator. Honest caveats: the persona assumes the gws-docs, gws-drive, gws-gmail, gws-chat and gws-slides utility skills are loaded and the gws binary is installed and authenticated; it's an operating mode, not automation β the agent still decides what to write and where to publish. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Prerequisites: a paid Google Workspace account; the gws CLI installed and authenticated; this persona also requires the gws-docs, gws-drive, gws-gmail, gws-chat and gws-slides utility skills loaded Install "Content Creator Persona (gws CLI)" for me. Operate as a content creator across Docs, Drive, Gmail, Chat and Slides Repository: https://github.com/googleworkspace/cli/blob/main/skills/persona-content-creator/SKILL.md 1. Fetch the SKILL.md file for the googleworkspace-persona-content-creator skill from the repository into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "googleworkspace-persona-content-creator". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. any accounts, API keys, or CLI tools mentioned in the prerequisites above). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. Never ask me to paste secrets in chat β credentials go through the secure vault or environment variables. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you β no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the sellerβs own page, usually Stripe.
What does the β next to a creatorβs name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself β always check a build before installing it.