agentleFS
googleworkspacegoogleworkspace/cli/skills/persona-content-creator/SKILL.md

persona-content-creator

Skill32k starsChanged 2 days agoApache-2.0View on GitHub

Create, organize, and distribute content across Workspace.

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create, organize, and distribute content across Workspace.

    line 23
  2. Very specific:

    Use gws docs +write for quick content updates — it handles the Docs API formatting.

    line 36
  3. Distinctive:

    Keep a 'Content Calendar' in a shared Sheet for tracking publication schedules.

    line 37
  4. Very specific:

    Use --format yaml for human-readable output when debugging API responses.

    line 38

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.

Download now (ZIP)

Trending

More talk lately.about the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 56 mentionsApr 2026: 8 mentionsMay 2026: 12 mentionsJun 2026: 9 mentionsJul 2026: 9 mentionsAug 2026: 4 mentionsSep 2026: 17 mentionsOct 2026: 6 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the googleworkspace/cli repository that our weekly crawl found. There is no adoption data for this file yet.

Who's talking about googleworkspace/cli

The biggest 5 of 121 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 121

Talked about on GitHub, Bluesky, YouTube, the web and Hacker News (121 times).

On GitHub · 50

45 more on GitHub

On Bluesky · 39

34 more on Bluesky

On YouTube · 23

18 more on YouTube

On Hacker News · 4

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.