googleworkspace/cli
85 skills1M installs2M starsGitHub
Install
npx skills add https://github.com/googleworkspace/cliSkills in this repo
1Gws Docsgws-docs is an agent skill for solo and indie builders who already use the Google Workspace CLI (gws) and want Docs API operations without writing raw REST calls. It documents how to invoke `gws docs <resource> <method>` for documents.create, documents.get, and documents.batchUpdate, including the rule that invalid batchUpdate requests fail the entire batch. Before any method call, the workflow points you at schema inspection so parameters and types match what Google expects. The skill explicitly defers authentication, global flags, and security posture to the companion gws-shared skill, which you should treat as a hard prerequisite in the same repo. For append-only edits, the table routes you to the gws-docs-write helper rather than re-deriving insert semantics. Install it when your agent needs to materialize blank docs, pull canonical document JSON, or apply structured updates during builds, handoffs, or lightweight doc automation—not when you only need browser-based editing.31.6kinstalls2Gws Drivegws-drive is an agent skill for the Google Workspace CLI that teaches models how to operate Google Drive v3 safely via `gws drive`. Solo and indie builders who already use Claude Code, Cursor, or Codex for shipping work install it when they want the agent to create folders, adjust permissions, resolve access proposals, or query capabilities without re-reading the entire Drive API reference each session. The skill assumes the `gws` binary is installed and that `../gws-shared/SKILL.md` has been read for authentication and field-selection rules Google requires on many endpoints. It catalogs API resources and methods in prose so the agent picks the right resource name, respects patch semantics, and chains to the dedicated upload skill when a file needs to land in Drive with metadata. It is not a full document editor or a backup product; it is procedural knowledge for command-shaped Drive automation inside an agent loop, which keeps repetitive file-admin tasks out of brittle one-off scripts.31.5kinstalls3Gws Calendargws-calendar packages Google Calendar v3 knowledge for agents that operate the Google Workspace CLI. Indie builders shipping SaaS with demos, support calls, or internal rituals use it when they want Codex, Cursor, or Claude Code to insert events, adjust calendar ACLs, or surface an agenda without pasting REST examples from Google's docs every time. Like sibling gws skills, it mandates reading gws-shared first so tokens, scopes, and security constraints stay consistent across Workspace commands. The README structures resources by API group—ACL rules, calendar list mutations, and links to focused helpers for insert and agenda views—so the model chooses patch versus update semantics and knows when to delegate event creation to the insert helper. Complexity is intermediate because OAuth, calendar IDs, and recurrence rules still need human verification. This skill does not replace a full scheduling product; it gives procedural, command-level guidance for automating Calendar from an agent session.30.1kinstalls4Gws Sheetsgws-sheets teaches your coding agent to operate Google Sheets through the Google Workspace CLI (gws). Solo builders install it when spreadsheets are the system of record—for funnel tabs, content calendars, inventory, or lightweight CRMs—and they want scripted reads and writes instead of manual UI work. The skill points to prerequisite gws-shared for authentication, global flags, and security constraints, then maps the spreadsheets API to shell commands including batchUpdate for validated multi-request updates, create for new workbooks, and get for metadata and optional grid data. Companion helpers append rows and read ranges without re-deriving API paths. Version 0.22.5 is declared in metadata. It is a phase-specific integration skill for Claude Code or similar agents that already use gws in the repo or CI environment.30.1kinstalls5Gws Docs WriteGWS Docs Write is an agent skill for solo builders who use the Google Workspace CLI to append text to existing Google Docs without opening the browser. It depends on the shared gws auth and security rules from gws-shared, documents required flags for document ID and text, and warns that this is a write operation that deserves user confirmation. Use it during Build when you are updating living specs, meeting notes, or handoff documents from an agent session. The skill is narrow by design: end-of-body plain-text insertion, with a pointer to batchUpdate when you need formatting. It pairs with the broader gws-docs read/write family for a complete Docs automation path.26.6kinstalls6Gws Sheets Readgws-sheets-read is a narrow integration skill for solo builders who already use Google Workspace CLI (gws) and want agents to fetch spreadsheet values deterministically. After satisfying prerequisites in gws-shared SKILL.md—authentication, global flags, and security rules—you run `gws sheets +read` with a spreadsheet ID and range. The operation is explicitly read-only, which makes it safe for pulling pricing tables, content calendars, lead lists, or config matrices into build-time scripts and agents. Examples cover full-sheet reads and bounded rectangles. When cell formatting or metadata matters, the skill notes that the raw Google Sheets values.get API remains the escape hatch. Pair it with other gws-sheets write skills only when you intentionally need mutating workflows elsewhere in the stack.26.5kinstalls7Gws Drive Uploadgws-drive-upload is a narrow Google Workspace CLI skill for solo builders who want agents to push artifacts—reports, CSV exports, PDFs—into Drive without hand-writing OAuth flows each time. It assumes the gws binary is installed and that you have read the shared gws-shared skill for authentication, global flags, and security constraints; the readme even points to gws generate-skills if that shared doc is missing. Usage is intentionally simple: one positional file path plus optional parent folder and display name flags, with MIME inference handled by the tool. Because uploads mutate remote state, the skill carries a caution to confirm with the user before running, which matters for agentic automation that might otherwise spray files into shared drives. It fits Build-phase integration work when you are connecting a SaaS backup, delivering generated documents to stakeholders, or scripting launch assets into a known folder. It is not a full Drive browser replacement, sharing ACL manager, or Google Apps Script IDE.26kinstalls8Gws Calendar Agendagws-calendar-agenda is a Google Workspace CLI agent skill that shows upcoming events across your calendars using gws calendar +agenda. It targets solo builders who already use the gws tool chain and want their coding agent to surface schedule context without opening the browser or editing events. The command is strictly read-only: it queries Google Calendar with optional windows (--today, --tomorrow, --week, or --days), narrows to a named calendar, and respects your account timezone with an IANA override when needed. Before use, the skill expects you to read ../gws-shared/SKILL.md for authentication, global flags, and security rules, or regenerate skills with gws generate-skills if that file is missing. Typical flows include a morning agenda pass before deep work, a week view before release planning, or feeding formatted tables into agent prompts for standup or support shifts. Install gws as a required binary and keep OAuth scopes minimal since the skill never mutates events.26kinstalls9Gws Calendar Insertgws-calendar-insert is a narrow Google Workspace agent skill that teaches your coding agent how to run `gws calendar +insert` to add events to Google Calendar. It targets solo and indie builders who already use the `gws` CLI to script Workspace tasks and want standups, reviews, or customer calls scheduled from chat or automation runs. The skill is explicit about prerequisites: read `../gws-shared/SKILL.md` (or regenerate skills with `gws generate-skills`) so OAuth, global flags, and security constraints are honored before any insert. Usage centers on three required parameters—summary, start, and end—with optional calendar targeting, location, body text, attendees, and an automatic Meet conference when you pass `--meet`. Examples show Pacific-offset RFC3339 timestamps, which reduces timezone mistakes that break agent-generated schedules. It is a task integration, not a planning methodology: you supply the event details; the skill ensures the command shape and flags match what `gws` expects.25kinstalls10Gws Gmail Sendgws-gmail-send is a thin agent skill wrapping the Google Workspace CLI Gmail send command so Claude Code, Cursor, or Codex can deliver email from a scripted workflow. Solo and indie builders use it when a ship or grow automation should notify a customer, escalate an alert to themselves, or fire a one-off outreach message without building a separate ESP integration. The skill documents required flags, attachment and HTML options, and safe patterns inherited from the shared gws skill package. It is phase-specific: most natural in Grow for lifecycle and support mail, though the same command fits Launch distribution or Operate incident comms. Install the gws binary and complete auth per gws-shared before invoking; treat OAuth scopes and recipient data as sensitive.24.9kinstalls11Gws Sheets Appendgws-sheets-append is a focused Google Workspace agent skill that lets solo and indie builders append data to an existing Google Sheet using the gws command-line tool. It is meant for lightweight operational analytics—logging signups, campaign rows, inventory counts, or agent-generated audit trails—without building a full ETL pipeline first. You pass a spreadsheet ID, optionally a sheet range in A1 notation, and either comma-separated values for a single row or a JSON array for multiple rows at once. Because it performs writes, the skill explicitly treats execution as user-confirmed, which matches how one-person teams should gate production spreadsheets. Install it when you already standardize on the googleworkspace/cli skill family and need a repeatable append primitive your coding agent can invoke safely. Read gws-shared first for OAuth and global flags; this skill is integration-shaped, not a replacement for Sheets API application design.24.5kinstalls12Gws Sharedgws-shared is the companion reference for the Google Workspace `gws` CLI that agents load when automating Drive, Gmail, Calendar, and related APIs from the terminal. Solo builders use it to keep authentication paths consistent—interactive login versus service accounts—and to apply the same output and safety conventions on every call. The skill spells out the `gws <service> <resource> <method>` shape, method-level flags for JSON bodies and file uploads, and pagination knobs so long lists do not silently truncate. It also encodes operational guardrails: prefer dry-run validation, paginate with explicit limits and delays, and treat destructive commands as user-confirmed actions. If you are stitching Workspace into scripts, CI, or agent workflows, this skill prevents one-off ad hoc CLI usage that leaks tokens or skips confirmation on mutating operations.23.4kinstalls13Gws Tasksgws-tasks is an agent skill that teaches models how to operate the Google Tasks API through the `gws` command-line client. Solo and indie builders install it when they want an AI assistant to maintain real task lists—creating lists, adding items, updating status, and clearing completed work—instead of keeping todos only in chat. The skill documents every supported resource method for tasklists and tasks, including edge cases such as assigned tasks that also appear in Google Docs or Chat. It explicitly depends on reading the companion gws-shared skill for authentication, global flags, and security rules, which keeps OAuth and credential handling consistent across the Google Workspace skill family. Use it during active build cycles when you are juggling features, bugs, and launch chores and already live in Google Workspace. It is a thin integration layer, not a planning methodology: you still decide priorities; the skill makes API operations reliable and repeatable for Claude Code, Cursor, Codex, and similar agents.22.6kinstalls14Gws Slidesgws-slides is an agent skill for solo builders who already use Google Workspace and want programmatic control over Google Slides without clicking through the UI. It documents the v1 `gws slides` CLI surface: creating blank presentations, fetching the latest revision, and applying structured batch updates where invalid requests fail the entire batch. The skill assumes you have installed the `gws` binary and read the companion gws-shared SKILL.md for OAuth and safety rules. It fits indie founders automating investor decks, workshop slides, or recurring status presentations from the same repo where their agent writes code. Discovery-first guidance (`--help`, method inspection) reduces wrong-parameter calls that waste API quota. It is narrower than a full Google Workspace suite skill—it is the Slides slice of the larger CLI ecosystem—so pair it with other gws-* skills when you need Docs, Drive, or Gmail in the same workflow.22.5kinstalls15Gws Meetgws-meet is an agent skill for solo builders and small teams who manage Google Meet programmatically through the Google Workspace CLI (`gws`). It does not replace the Meet UI; it teaches your coding agent the correct resource names, methods, and flags for Meet API v2—creating and updating meeting spaces, ending active conferences, and listing or drilling into conference records, participants, recordings, smart notes, and transcripts. Install it when you are building automations, ops scripts, or agent workflows that must create spaces, fetch post-meeting artifacts, or audit conferences without clicking through admin consoles. The skill explicitly chains to gws-shared for OAuth, global flags, and security constraints, so credentials and scope stay consistent across Calendar, Drive, and Meet skills in the same repo. Complexity is intermediate because you need Workspace API access, the `gws` binary on PATH, and comfort with REST-shaped CLI verbs rather than a single high-level “schedule meeting” command.20.5kinstalls16Gws Gmail WatchGws Gmail Watch documents how to run the gws gmail +watch command so coding agents can treat the inbox as a live event source. Output is NDJSON by default, with knobs for Gmail message format, batch size, poll interval, and Gmail label filters such as INBOX and UNREAD. Solo builders building support bots, lead routers, or personal chief-of-staff agents can point watch at a GCP project to provision or reuse Pub/Sub topic and subscription resources, or attach an existing subscription to skip setup. Flags support a one-shot pull for tests, streaming writes to an output directory, and cleanup of created Pub/Sub assets on exit. The skill stresses reading gws-shared first for OAuth and security constraints. It is an integration reference, not a full incident-response runbook.20.3kinstalls17Gws Formsgws-forms is an agent skill that wraps Google Forms API v1 operations behind the Google Workspace CLI (gws). Solo and indie builders who already standardize on gws for Drive, Sheets, or Gmail can extend the same auth and flag patterns to read and write forms without writing bespoke HTTP clients in every project. The skill documents resource methods including batchUpdate, create, get, setPublishSettings, plus nested responses and watches, and stresses an important API constraint: create only copies title and document title, so real surveys must follow create with batchUpdate or update. Before any call, it directs agents to inspect schemas with gws schema so parameters and defaults match the live API. Install it when your workflow needs programmatic form creation, publish toggles, or response polling inside Claude Code, Cursor, or Codex, and pair it with gws-shared so tokens and scopes stay consistent across Workspace skills.20.1kinstalls18Gws Keepgws-keep is an agent skill for managing Google Keep through the googleworkspace gws CLI. Solo and indie builders use it when quick capture matters: parking lot ideas, research links, launch checklists, and support callbacks that should stay in Keep instead of bloating the repo. The skill maps the Keep API surface—creating and listing notes, fetching single notes, deleting with OWNER constraints, permission operations, and downloading attachments when alt=media is required. Pagination is opaque token-based, which suits agents that need to drain a note backlog incrementally. It is a multi-phase productivity integration: valuable during Idea research, Validate scoping conversations, Grow content planning, and Operate support triage. Always pair it with gws-shared so authentication and security rules are consistent across the Workspace skill pack. Complexity stays beginner-to-intermediate because the CLI abstracts REST details, but destructive deletes demand human judgment.19.2kinstalls19Gws Gmail Replygws-gmail-reply is an agent skill that wraps the Google Workspace CLI `gws gmail +reply` command so coding agents can answer inbound mail with correct threading. Solo and indie builders who already authenticate through the shared gws skill can pass a message ID and body, optionally override From for send-as aliases, add recipients, attach files, or save a draft instead of sending. Plain text is default; HTML mode treats the body as markup. A dry-run flag shows what would be sent without executing, which is useful before an agent touches a live customer thread. Install it when support and lifecycle email should stay in terminal-driven workflows alongside other gws Gmail helpers rather than custom API scripts.17.5kinstalls20Gws Workflowgws-workflow is a Google Workspace automation skill built around the `gws` CLI. It exposes cross-service productivity flows—today’s meetings plus open tasks for standup, next-meeting prep with agenda and docs, turning Gmail into Google Tasks, a weekly meetings-and-unread-mail digest, and announcing Drive files in Chat. Solo builders and tiny teams who already standardize on Workspace can treat these helpers as agent-invokable rituals instead of copying between apps. Before any API call, the skill directs you to `gws workflow --help` and `gws schema workflow.<resource>.<method>` so agents build correct `--params` and `--json` flags. It depends on the shared gws auth and security guidance in gws-shared and pairs with sibling helper SKILL.md files for each plus-command. Complexity is intermediate because you need the gws toolchain installed and comfortable reading schema output.17.4kinstalls21Gws ChatGws Chat is an agent skill for solo builders automating Google Workspace who need programmatic control of Google Chat spaces and messages through the Google Workspace CLI. It assumes you have installed the `gws` binary and absorbed the shared authentication, global flags, and security guidance from the companion gws-shared skill—generating skills via `gws generate-skills` when that file is missing. The documented interface follows `gws chat <resource> <method>` against Chat API v1, including custom emoji lifecycle operations with administrator and Workspace eligibility caveats from Google’s help articles. A helper command table routes high-frequency work such as sending a space message to the dedicated send skill. This is reference-style integration knowledge for agents orchestrating team notifications or chat ops, not a standalone hosted connector.17kinstalls22Gws Workflow Email To Taskgws-workflow-email-to-task is a focused Google Workspace workflow skill for agents and terminal users who want Gmail messages promoted into Google Tasks without retyping subjects and snippets. It wraps `gws workflow +email-to-task` with clear flags: mandatory message ID, optional task list ID defaulting to @default. The mapping convention—subject as title, snippet as notes—keeps tasks lightweight and faithful to the source mail. Unlike the weekly digest sibling, this workflow writes data (new task entries), so the SKILL.md explicitly recommends user confirmation before execution—a good fit for solo builders who want human-in-the-loop safety. Prerequisites mirror other gws workflow skills: install the gws binary, read gws-shared for OAuth and global flags, and use the parent gws-workflow index for related commands. It supports operate-phase inbox zero habits and build-phase agent automations that turn customer email into trackable follow-ups.16.9kinstalls23Recipe Create Presentationrecipe-create-presentation is a short Google Workspace CLI recipe that creates a new Google Slides presentation and optionally shares it with a collaborator. Solo builders and tiny teams who already use the `gws` tool can run it from an agent without clicking through Slides UI—handy when quarterly reviews, pitch decks, or status slides are part of shipping. The flow is deliberate: load `gws-slides`, create the deck with a JSON title, read the presentation ID from the response, then add a Drive writer permission for a teammate email. It is a recipe slice of the broader googleworkspace/cli catalog, not a full Slides authoring system—no slide layout automation beyond initial creation. Best when OAuth and `gws` are configured and you need a repeatable agent-driven bootstrap for a new deck.16.8kinstalls24Gws Workflow Meeting Prepgws-workflow-meeting-prep is a Google Workspace CLI workflow skill that prepares you for the next calendar meeting using the gws binary. Solo builders running agents in Claude Code, Cursor, or similar environments install it to avoid hand-rolling Calendar API calls when they only need a fast, read-only briefing: who is attending, what the description says, and which calendar slice to use. It depends on the shared gws-shared skill for authentication, global flags, and security conventions, and exposes standard formatting switches so agent output can feed downstream planning or note-taking steps. The workflow is intentionally non-destructive, which makes it safe for daily standup prep, investor calls, or customer success syncs while you are still in Build phase wiring productivity automations. Treat it as one command in a broader gws workflow family rather than a full meeting-notes or CRM integration.16.6kinstalls25Gws Peoplegws-people is a narrow Google Workspace CLI skill that teaches an agent how to manage People API contacts and contact groups using the `gws` command-line tool. Solo builders use it when automating contact list maintenance, syncing CRM-like groupings into Google Contacts, or scripting profile lookups as part of a larger Workspace integration. The SKILL.md explicitly defers authentication, global flags, and security posture to the sibling gws-shared skill, and lists concrete resources such as contactGroups with methods from batchGet through update, including operational notes about sequential mutates per user to avoid latency and failures. It is phase-specific to Build integrations: you need the gws binary installed, Workspace credentials configured per shared rules, and a clear automation goal. It is not a full CRM replacement or a UI builder; it is command surface documentation for agents that already run gws in CI or local workflows.16.5kinstalls26Gws Workflow Standup Reportgws-workflow-standup-report packages a Google Workspace cross-service workflow that assembles a standup-oriented snapshot: meetings scheduled for today and open tasks from Google Tasks. Solo and indie builders use it to start the day with agent-readable output instead of clicking through Calendar and Tasks separately. Before running, the skill points you to gws-shared for authentication, global flags, and security expectations—generate via gws generate-skills if that file is missing. Output defaults to JSON but supports table, YAML, and CSV for pasting into notes, Slack, or a daily log. Because it is explicitly read-only, it fits automated morning briefings in Operate while still helping Validate scope conversations and Build pm checkpoints when you need ground truth on commitments versus calendar load.16.4kinstalls27Gws Workflow Weekly Digestgws-workflow-weekly-digest is a Google Workspace CLI workflow skill that packages a weekly operator ritual into one agent-invokable command. Solo builders and indie operators who live in Gmail and Calendar can ask their coding agent to run the digest instead of tab-hopping across Google surfaces. The workflow aggregates this week’s meetings from the calendar agenda with an unread email count summary from Gmail triage logic exposed by the gws toolchain. Execution stays read-only, which keeps blast radius low when agents run on a schedule or on demand. Before use, the agent should load gws-shared for OAuth, global flags, and security guardrails (or regenerate skills with `gws generate-skills` if that file is missing). Optional `--format` switches help pipe results into dashboards, spreadsheets, or human-readable standups. It is a narrow integration skill—not a full PM system—but it slots cleanly into morning reviews, Friday retros, and lightweight operate-phase habits.16.4kinstalls28Gws Gmail Readgws-gmail-read is a Google Workspace CLI agent skill that loads a single Gmail message and returns its body or headers for solo builders automating inbox triage. It expects the shared `gws` binary and the companion gws-shared auth rules documented in the same repo. Use it when an agent already has a message ID from search or webhooks and must extract readable text, structured JSON, or explicit headers before summarizing, classifying, or replying. Flags cover plain text versus HTML body, JSON output for pipelines, and dry-run safety. The skill pairs naturally with other gws-gmail commands for send and manage flows. It is a narrow integration, not a full mailbox client—ideal for scripted support and lifecycle automations where Gmail is the source of truth.16.4kinstalls29Recipe Create Gmail FilterRecipe Create Gmail Filter is a short procedural skill for solo builders who already use the Google Workspace CLI (`gws`) and the companion `gws-gmail` skill. It walks an agent through listing existing labels, creating a new label when needed, posting a filter with JSON criteria and actions, and listing filters to confirm the rule landed. The pattern fits indie operators who want receipts, newsletters, or client mail auto-sorted instead of manual drags each morning. You run it from the terminal via authenticated `gws` calls, so it pairs naturally with Claude Code, Cursor, or Codex agents that can execute shell steps. Expect intermediate setup: OAuth or service account for Gmail, correct userId (typically `me`), and label IDs from the list step before wiring `addLabelIds`. It is a recipe, not a full Gmail skill—load prerequisites first, then execute the numbered flow end to end.16.3kinstalls30Persona ResearcherPersona-researcher is an OpenClaw persona skill for solo builders who want their coding agent to behave like a disciplined researcher using the `gws` CLI against Google Workspace. It does not replace a dedicated reference manager; instead it wires Drive, Docs, Sheets, and Gmail into one repeatable workflow: store papers and notes in Drive, draft summaries with Docs, append structured logs to Sheets, announce files to collaborators, and request reviews over email. You install it when discovery and synthesis are scattered across chats and local folders and you already use or plan to use the googleworkspace CLI skills. Version 0.22.5 ships with persona metadata that enforces the four utility skills as prerequisites, so the agent does not half-implement research ops without Drive or Gmail access. Intermediate complexity reflects multi-skill orchestration rather than a single API call.16.2kinstalls31Persona Project ManagerPersona Project Manager is an OpenClaw persona skill for the googleworkspace/cli stack that turns your agent into a lightweight PM over Google Workspace. Before any coordination, you load gws-drive, gws-sheets, gws-calendar, gws-gmail, and gws-chat so the persona can run real CLI commands rather than vague reminders. The intended rhythm starts with gws workflow +weekly-digest for meetings and unread items, continues with Sheets append for status logs, Drive upload plus file-announce for artifacts, Calendar insert for recurring standups, and Gmail send for stakeholder updates. It targets indie builders and tiny teams who already live in Workspace and want one scripted operating cadence instead of tab-hopping. Metadata pins version 0.22.5 and requires the gws binary on PATH. Tips cover Drive search queries, jq pipes, and dry-run previews—signals this is production-adjacent automation with write access to your org data.16.2kinstalls32Gws Eventsgws-events is a Google Workspace CLI skill for solo builders who automate inbox, calendar, or Drive-adjacent workflows with agents. It assumes you already use the `gws` tool and have read the shared auth and security SKILL; if `gws-shared` is missing, the doc says to run `gws generate-skills` first. You invoke workspace event APIs through familiar CLI shapes—create or delete subscriptions, poll operations, and use streaming message calls—while dedicated subscribe and renew companions handle NDJSON event streams and keeping subscriptions active. It fits indie builders stitching Google Workspace into custom ops tooling without hand-maintaining every REST path. Treat credentials and subscription scopes as production secrets; review Prism security audits on this listing before piping live tenant data through an agent.16.2kinstalls33Gws Chat Sendgws-chat-send is an agent skill for the Google Workspace CLI (`gws`) that posts a plain-text message to a Google Chat space. Solo and indie builders use it when they want deploy notes, agent status, or team pings in Chat without maintaining custom REST clients. The workflow is intentionally minimal: discover a space name, then run `gws chat +send` with `--space` and `--text`. Before any send, the agent should read gws-shared for authentication and treat the command as a write operation that requires explicit user confirmation. The skill does not cover cards, threaded replies, or rich formatting—those paths point to the raw Chat API. It pairs naturally with listing spaces and the broader gws-chat command family for managing Chat from the terminal inside Claude Code, Cursor, Codex, or similar agents.16.2kinstalls34Persona Exec Assistantpersona-exec-assistant packages how a solo founder or indie operator can behave like an executive assistant inside Google Workspace, using the gws CLI instead of clicking through five apps. Before any session, the skill tells the agent to load gws-gmail, gws-calendar, gws-drive, and gws-chat, then run repeatable workflows such as gws workflow +standup-report for the day’s agenda, gws workflow +meeting-prep before calls, and gws workflow +weekly-digest for Monday planning. Inbox work flows through gws gmail +triage with a cap of ten messages, prioritizing direct reports and leadership, while scheduling uses gws calendar +agenda for conflict checks before gws calendar +insert. The tone guidance keeps drafts concise and professional, with an explicit human gate: confirm calendar changes with the executive before committing. It fits whenever your agent should operationalize email and calendar load across the journey, not only during a single launch week.16.1kinstalls35Recipe Backup Sheet As Csvrecipe-backup-sheet-as-csv is an agent skill that walks a solo builder through exporting Google Sheets data to CSV using the Google Workspace CLI (`gws`). It is aimed at indie operators who already rely on Sheets for ops, finance, or content trackers and need a repeatable agent procedure instead of manual File → Download. The recipe explicitly requires loading `gws-sheets` and `gws-drive` first, then offers two paths: Drive export with mimeType text/csv or a sheets +read invocation that returns CSV for a range like Sheet1. Use it when you need local backups before migrations, nightly dumps for scripts, or a CSV feed for another tool. It does not design schemas or validate business logic—it orchestrates authenticated CLI steps so your coding agent does not guess API shapes or skip dependent skills.16.1kinstalls36Recipe Save Email Attachmentsrecipe-save-email-attachments is a Google Workspace CLI recipe that teaches an agent to find Gmail messages with attachments and land those files in a specific Drive parent folder. Solo builders use it when invoicing, contracts, or deliverables pile up in email and manual saves are error-prone. The skill does not replace the Gmail or Drive skills—it assumes you load gws-gmail and gws-drive first, then run a fixed four-step command sequence: list messages matching a query, get the message payload, pull the attachment bytes, and upload with an explicit parent folder id. It fits indie operators who already authenticate gws on their machine and want a documented, repeatable handoff from inbox to cloud storage without writing a one-off script. Expect shell access, live Google APIs, and careful handling of message and attachment ids from prior list/get steps.16kinstalls37Recipe Organize Drive FolderRecipe Organize Drive Folder is a focused googleworkspace/cli recipe that scripts a clean Google Drive hierarchy for a named project such as Q2 Project. It assumes you have already loaded gws-drive and the gws CLI on your machine, then walks through creating a root folder, nesting Documents-style subfolders with explicit parent IDs, moving stray files by updating parent relationships, and listing children to confirm layout. Solo builders use it when a shared Drive has become a flat dump before onboarding a contractor or archiving deliverables. Commands are JSON-driven create and update calls with quoted query params, matching the rest of the gws skill family. The skill is narrowly scoped—no Sheets or Calendar—so it pairs well after broader PM personas or before file-announce workflows. Intermediate complexity reflects need to handle real file and folder IDs safely.16kinstalls38Recipe Find Free Timerecipe-find-free-time is a compact OpenClaw recipe for solo builders who already use the Google Workspace CLI (gws) and want agents to schedule meetings without manual calendar hunting. It chains a freebusy query across multiple users, human or agent review of overlapping gaps, and an insert command that books the slot with attendees. The skill explicitly depends on gws-calendar, so Prism users should treat this as one node in a small skills stack rather than a standalone calendar expert. It fits multi-phase use: you implement it during Build when connecting Workspace, then invoke it throughout Grow and Operate whenever coordination volume rises. The value is predictable CLI steps agents can repeat instead of improvising OAuth scopes and API shapes on every scheduling request.16kinstalls39Recipe Create Doc From Templaterecipe-create-doc-from-template is an OpenClaw recipe skill for Google Workspace that walks your agent through copying a Google Docs template, writing structured markdown-style sections into the new file, and sharing it with collaborators. It is aimed at solo and indie builders who already use the gws CLI and want repeatable project briefs, launch notes, or handoff docs without manual Drive UI steps. You should invoke it when you have a known template doc ID and need a named copy plus team access in the same session. The skill chains explicit shell commands across Drive and Docs APIs, so it fits agents that can run gws after the sibling gws-drive and gws-docs capabilities are loaded. It matters because it turns ad-hoc “make me a doc” requests into a auditable, parameter-driven workflow that scales across launches and client work.15.9kinstalls40Recipe Plan Weekly Schedulerecipe-plan-weekly-schedule is a short OpenClaw recipe for solo builders who already use Google Workspace from the terminal. It walks an agent through loading gws-calendar, pulling the current week’s agenda, running a free/busy query across a time window, inserting one or more calendar events to fill gaps, and confirming the updated week view. The skill is intentionally procedural rather than open-ended chat: each step maps to a documented gws subcommand so outcomes are repeatable in Claude Code, Cursor, or Codex sessions. It matters for indie builders who batch client work and need agent-assisted time blocking without opening the Calendar UI. Pair it with other gws-calendar recipes once event CRUD is familiar; it does not replace full project planning or task managers.15.9kinstalls41Recipe Compare Sheet TabsRecipe Compare Sheet Tabs is a Google Workspace CLI recipe that teaches an agent to pull two ranges from different tabs in one spreadsheet and reason about differences. It is built for solo builders and small teams who live in Sheets for lightweight CRMs, revenue trackers, or content calendars and need a repeatable compare ritual instead of manual eyeballing. You load the gws-sheets skill first, then issue two read commands with tab-qualified ranges such as January!A1:D and February!A1:D. The agent holds both datasets in context and identifies additions, removals, and cell-level changes. It fits the operate phase when you reconcile recurring reports, validate imports, or sanity-check a co-founder’s edits before you change formulas or downstream automations. It is not a full ETL pipeline—pair it with your own rules for keys and tolerance on numeric drift.15.9kinstalls42Recipe Bulk Download Folderrecipe-bulk-download-folder is a gws recipe for listing all files under a Google Drive folder and saving them locally, including exporting native Google Docs to PDF. You must load gws-drive first. Step one queries files whose parent is your folder ID; step two downloads each file by fileId; step three handles Docs with the export endpoint and application/pdf mime type. Solo builders use it when migrating client deliverables, snapshotting shared drives before churn, or feeding local tooling without manual Drive downloads. Intermediate complexity: pagination, many file IDs, and mixed MIME types need careful scripting beyond the sample loop.15.9kinstalls43Gws Workflow File AnnounceGws Workflow File Announce is a Google Workspace CLI skill for cross-service productivity: it announces an existing Drive file in a Google Chat space using file ID and space name. Solo builders shipping decks, one-pagers, beta builds, or policy docs use it when the bottleneck is telling the team where the file lives—not uploading it. The skill documents required flags, optional custom message text, and format switches, and notes that it is a write operation that posts to Chat while resolving the display name from Drive. Read gws-shared first for auth, global flags, and security rules, or regenerate skills with gws generate-skills if shared docs are missing. Typical flow: upload via drive +upload, then file-announce to spaces/SPACE_ID. It complements public launch channels by tightening internal distribution during ship and launch weeks.15.9kinstalls44Recipe Draft Email From DocRecipe Draft Email from Doc is a Google Workspace CLI recipe for solo builders who keep long-form copy in Google Docs and want to ship it as email without manual copy-paste. After loading the gws-docs and gws-gmail skills, the agent fetches document content with gws docs documents get, pulls text from the body, and sends or drafts via gws gmail +send with your subject and recipient. It fits indie newsletters, changelog blasts, and one-off stakeholder updates when Gmail and Docs already live in your workspace. The flow is intentionally linear—no separate templating layer—so you trade formatting fidelity for speed when the Doc is the source of truth.15.8kinstalls45Gws Events Renewgws-events-renew is a narrow Google Workspace CLI skill for reactivating Workspace Events subscriptions before they lapse. Solo builders and small teams use it when event-driven automations (mail, drive, or other Workspace notifications) depend on the gws events API and subscriptions must be refreshed on a schedule. The skill documents the gws events +renew command, flags for targeting one subscription or every subscription expiring inside a time window, and practical tips such as wiring --all into cron. It explicitly depends on the shared gws auth and flag conventions in gws-shared, and points to the broader gws-events command family. This is an integration skill for operators already using the gws binary—not a substitute for designing the original subscription or webhook handlers.15.8kinstalls46Gws Events Subscribegws-events-subscribe is an agent skill for the Google Workspace CLI that turns Workspace Events into a pull-and-stream workflow for solo builders automating Chat, Calendar-adjacent resources, and other Workspace surfaces. You point `--target` at a resource URI, choose `--event-types`, and optionally bind a GCP project and Pub/Sub subscription so events arrive as NDJSON in the terminal or on disk. It fits indie builders who already use `gws` for Google APIs and want event-driven hooks for agents, scripts, or small SaaS backends without maintaining custom subscription code. Prerequisite reading in gws-shared covers auth, global flags, and security expectations. Use when you need live Workspace signals for notifications, audit logs, or orchestration—not for one-off REST reads.15.8kinstalls47Persona Content Creatorpersona-content-creator is a multi-skill persona for solo builders and indie marketers who live in Google Workspace and want one agent identity for the full content loop. Instead of juggling disconnected CLI skills, you load gws-docs, gws-drive, gws-gmail, gws-chat, and gws-slides as prerequisites, then follow a single playbook: write in Docs, file assets in Drive, ping stakeholders in Chat, and route approvals through Gmail. The skill highlights the file-announce workflow for broadcasting ready deliverables and recommends a shared Sheet-based content calendar for publication timing. Tips cover human-readable `--format yaml` debugging and leaning on `gws docs +write` for quick edits without hand-crafting API requests. It is ideal when you are compounding organic reach, newsletter drafts, or launch collateral without a dedicated ops hire.15.8kinstalls48Recipe Email Drive LinkRecipe Email Drive Link packages a common solo-builder handoff: locate a Google Drive file, share it with the right person as a reader, and email them the link with a short message. It depends on the `gws` binary plus loaded `gws-drive` and `gws-gmail` skills, so your agent issues search, permission, and send commands instead of copying links manually. The flow suits freelancers sending reports, founders sharing specs, or tiny teams distributing docs after a build milestone. Search uses Drive `files.list` with a name query; sharing uses `permissions.create` with fileId; delivery uses `gws gmail +send` with to, subject, and body. You need file IDs from the search step and must respect your org's sharing policies. Intermediate complexity reflects multi-skill prerequisites and correct ID threading across steps.15.8kinstalls49Recipe Generate Report From Sheetrecipe-generate-report-from-sheet is a Google Workspace CLI recipe skill for solo builders and indie operators who live in Sheets but need polished Docs deliverables without manual copy-paste. After you load the companion gws-sheets, gws-docs, and gws-drive skills, the agent walks a fixed four-step flow: read a bounded range from a spreadsheet, create a titled Google Doc, inject a structured report (summary plus ranked sections), and share read access with a specific email. It assumes the gws binary is installed and you already have sheet IDs and ranges. The pattern suits weekly sales rollups, funnel snapshots, or any tabular export that should become a dated narrative report. Because it is recipe-shaped rather than open-ended API exploration, agents stay on-path and produce repeatable documentation artifacts stakeholders can open in Drive.15.8kinstalls50Gws Admin Reportsgws-admin-reports is an agent skill that documents how to call Google Workspace Admin Reports APIs through the Google Workspace CLI (`gws`). Solo builders and small teams use it when they need administrator console or Drive activity listings, customer-wide usage report snapshots, or entity-scoped usage metrics without writing bespoke SDK clients. The skill points to prerequisite reading in gws-shared for authentication and safe flag usage, then maps each resource—activities, channels, customerUsageReports, and entityUsageReports—to concrete subcommands. That makes it practical for Operate-phase monitoring and Grow-phase analytics when you are reconciling licenses, investigating suspicious admin actions, or exporting usage properties for internal dashboards. It is an integration surface, not a hosted report UI; you still own query parameters, pagination, and storing results.15.7kinstalls51Recipe Watch Drive Changesrecipe-watch-drive-changes is a short procedural skill that walks a solo builder through subscribing to Google Drive change notifications using the Google Workspace CLI. It assumes you have already loaded gws-events and the `gws` binary, then gives copy-ready commands to create an events subscription against a Drive target resource, route notifications to a Pub/Sub topic, optionally include resource payloads, list active subscriptions, and renew a subscription before it expires. The pattern fits indie SaaS builders who sync files, trigger rebuilds, or kick agent workflows when shared drives change. It is a recipe layer on top of lower-level gws-events skills rather than a standalone auth or SDK reference, so you should treat Pub/Sub topic provisioning and IAM as your own infrastructure work outside the four documented steps.15.7kinstalls52Recipe Label And Archive Emailsrecipe-label-and-archive-emails documents a three-step Gmail workflow for the Google Workspace gws CLI: list messages matching a query such as from:notifications@service.com, add a label by ID, then remove the INBOX label to archive while preserving the thread. Solo builders use it to turn repetitive inbox rules into explicit commands an agent can execute after loading the gws-gmail skill. The recipe stays narrow—search, label, archive—so you supply the label ID and message IDs from list results. It fits when notification or vendor mail should leave the inbox but remain searchable under labels. Pair with your real label taxonomy and safer dry runs on a single MESSAGE_ID before bulk changes.15.6kinstalls53Persona Team LeadPersona Team Lead is an OpenClaw persona skill for the Google Workspace CLI (gws) that turns your agent into a coordination layer for small teams. Before use, you load the utility skills for Calendar, Gmail, Chat, Drive, and Sheets so calendar pulls, email triage, chat posts, and sheet updates stay in one playbook. Daily standups run through gws workflow +standup-report with output shared in team Chat; 1:1s use +meeting-prep; leadership snapshots use +weekly-digest; and inbox follow-ups convert with +email-to-task. Solo and indie builders who act as tech lead plus people lead get repeatable rituals without hopping between five Google UIs. The skill is opinionated about workflow commands rather than ad-hoc API calls, which keeps permissions and auditing aligned with the rest of the gws skill family.15.6kinstalls54Recipe Create Shared DriveRecipe Create Shared Drive guides an agent through provisioning a Google Shared Drive, inviting a member with writer access, and listing permissions to confirm membership. It targets solo founders who suddenly need a durable team folder separate from My Drive—client projects, contractor collaboration, or agency vaults. You need the `gws` CLI and the `gws-drive` skill loaded first. Creation passes a unique `requestId` and display name JSON; membership uses `permissions.create` on the drive ID with `supportsAllDrives` enabled, which is easy to miss in ad-hoc scripts. The recipe is version 0.22.5 in metadata and stays deliberately short: create, add, verify. Intermediate difficulty reflects Workspace admin constraints, correct roles, and understanding drive IDs versus file IDs.15.6kinstalls55Recipe Create Task Listrecipe-create-task-list teaches an agent to stand up a Google Tasks list and seed it with work items using the Google Workspace CLI. After loading the gws-tasks skill, you run a task list insert, add tasks with titles, optional notes, and due timestamps, then verify with a table-formatted list command. Indie builders use it to mirror Q2 goals, review checkpoints, or agent-generated action items inside Workspace instead of a separate todo app. The skill is intentionally narrow: it does not replace full project management methodology, but it gives repeatable commands for list creation and task CRUD entry points. Pair it with gws-tasks for parameter details and ensure OAuth scopes cover Tasks for the account you automate.15.6kinstalls56Recipe Block Focus Timerecipe-block-focus-time is a Google Workspace CLI recipe that walks an agent through creating recurring focus time on your primary Google Calendar using gws calendar events insert, then confirming the block appears busy via gws calendar +agenda. It targets indie builders who protect deep work with calendar hygiene instead of informal mental rules. The SKILL.md marks it as a recipe requiring the gws binary and the gws-calendar skill loaded first, with explicit JSON for summary, description, weekly recurrence on Monday through Friday, and opaque transparency. Use it when you want durable, inspectable commands your agent can replay after you standardize timezone and hours. It does not replace a full calendaring strategy—pair it with your real meeting load and adjust RRULE or times in the JSON payload.15.6kinstalls57Recipe Schedule Recurring EventSchedule Recurring Event is a Google Workspace CLI recipe skill that tells your agent exactly how to spin up a repeating calendar meeting with attendees. It assumes the gws binary is installed and that you have already loaded the gws-calendar skill, which owns the underlying calendar commands. The flow is deliberately short: construct an events insert call with calendarId primary, weekly RRULE, timezone-aware start and end, and teammate emails, then confirm creation by listing the next fourteen days in table format. Solo builders automating standups, client check-ins, or launch-week rituals use it when they want repeatable shell commands instead of clicking through Calendar UI. It fits agent-driven DevOps-style workflows where recipes compose larger playbooks. Complexity is beginner-facing because parameters are copy-paste JSON, but OAuth and gws setup live in the prerequisite calendar skill.15.6kinstalls58Recipe Find Large Filesrecipe-find-large-files is a short Google Workspace CLI recipe for solo builders hitting Drive storage limits or cleaning up before billing surprises. It assumes you have already loaded the gws-drive skill and the gws tool on PATH. Step one runs a sized query against Drive’s API ordering by quota bytes, returning twenty rows with identifiers and owners in a table. Step two is human-or-agent judgment on what to archive or move— the recipe stops at visibility, not automatic deletion. Version 0.22.5 ships with the googleworkspace/cli skill pack. Use it in Operate when quota alerts fire or during periodic workspace housekeeping, not when authoring new Apps Script integrations.15.6kinstalls59Recipe Share Doc And NotifyRecipe Share Doc And Notify is a Google Workspace CLI agent skill that turns a common solo-builder chore—share the spec, ping the reviewer—into three copy-paste gws commands. It finds a document by title query, creates a Drive permission with writer access for one collaborator, then sends Gmail with the doc URL. The recipe declares OpenClaw category recipe and domain productivity, and hard-requires the gws CLI plus gws-drive, gws-docs, and gws-gmail skills loaded first. Solo founders use it when validating scope with a contractor, handing off build briefs, or running lightweight PM without Zapier. It is phase-specific integration glue: not journey-wide methodology. You need Google APIs authenticated for gws on your machine or agent environment. Outputs are shared access and a sent notification email, not edited doc content. Pair with broader Drive or Gmail skills when you must create the doc from scratch or thread follow-ups.15.5kinstalls60Recipe Copy Sheet For New Monthrecipe-copy-sheet-for-new-month automates the boring start-of-month Google Sheets ritual for solo builders who track metrics, finances, or content in a tab-per-month workbook. After loading gws-sheets, you fetch spreadsheet metadata, copy the template sheet with copyTo into the same spreadsheet, then rename the new tab via spreadsheets batchUpdate. It assumes you know spreadsheetId and the numeric sheetId of your template. Ideal for indies maintaining OKR sheets, freelance hour logs, or editorial calendars who want agent-run commands instead of manual Duplicate and rename. Intermediate complexity because sheetIds change after copy and title fields must match your calendar.15.5kinstalls61Recipe Batch Invite To EventRecipe Batch Invite To Event is a short Google Workspace workflow for agents that already know a Calendar event ID and need to add several people at once. It walks through fetching the event with gws calendar events get, applying a patch that sets an attendees array and sendUpdates so invitees receive notifications, then re-fetching to confirm the list. Solo and indie builders shipping agent automations for customer success, community calls, or internal standups can paste emails into one command instead of clicking through Google Calendar. The skill is explicit that gws-calendar must be loaded first and that gws must be on PATH. It is a procedural companion to the broader calendar skill, not a substitute for OAuth setup or calendar discovery.15.5kinstalls62Recipe Collect Form ResponsesRecipe Collect Form Responses is a compact Google Workspace procedure for retrieving Google Form data through the gws CLI. When you do not remember the formId, step one lists available forms; step two loads form structure; step three pulls all responses with an optional table layout for quick scanning. Indie builders validating ideas use it to turn waitlist or survey submissions into something an agent can summarize, compare, or feed into a scope doc—without exporting CSVs manually. The recipe assumes gws-forms is already available for auth and command patterns. It documents read-oriented operations only and does not create forms or edit questions.15.4kinstalls63Recipe Create Events From Sheetrecipe-create-events-from-sheet is a short agent recipe for solo builders and small teams who already use the Google Workspace CLI (`gws`) and want spreadsheet-driven scheduling. After loading the companion skills `gws-sheets` and `gws-calendar`, the agent reads event rows from a named range on a spreadsheet, then loops each row to create matching Google Calendar entries with summaries, time bounds, and attendees. It is ideal when standups, interviews, or campaign dates live in Sheets but must appear on a shared calendar without maintaining duplicate manual entry. The skill does not invent API credentials or sheet layouts—it assumes you know the spreadsheet ID and column mapping implied by your range. Use it during integration work once event data is structured; pair with broader `gws` skills for auth, error handling, and idempotent reruns if you re-import the same sheet.15.4kinstalls64Recipe Review Overdue Tasksrecipe-review-overdue-tasks is a short OpenClaw recipe skill for solo builders who already run Google Workspace through the gws CLI and the gws-tasks skill. It walks an agent through listing task lists, pulling open tasks for a chosen list, and scanning due dates to surface work that is past due. You install it when manual Checks in Google Tasks are easy to skip and you want a repeatable, terminal-first review you can slot into daily or weekly operate rituals. The skill does not replace task creation, syncing, or OAuth setup—that lives in gws-tasks. It is intentionally narrow: find overdue incomplete tasks and make them visible in table output so you can prioritize, reschedule, or close them. Fit is strongest for indie operators who centralize todos in Google Tasks and automate ops with agent skills rather than opening the web UI every time.15.4kinstalls65Persona It Adminpersona-it-admin is an OpenClaw persona skill that tells an agent how to behave as a Google Workspace IT administrator. It requires loading utility skills gws-gmail, gws-drive, and gws-calendar first, then following a short playbook: open with the standup-report workflow, watch suspicious logins and audit logs, and tighten Drive sharing to match org security. Tips emphasize dry-run on bulk changes and checking `gws auth status` so service account permissions stay valid. For solo founders wearing an admin hat on a one-person Google domain, this packages repeatable governance language agents can follow instead of ad-hoc admin console clicking. It is not a full SOC2 checklist—it orients daily monitoring and policy moves on top of the gws CLI ecosystem at metadata version 0.22.5.15.4kinstalls66Recipe Create Meet SpaceRecipe Create Meet Space is a Google Workspace CLI orchestration skill for solo and indie builders who already use the gws tool and want a repeatable way to stand up a Meet conference and distribute the link. It is not a standalone installer: you must load the gws-meet and gws-gmail skills and have the gws binary on PATH before running the three documented steps. The flow creates an open meeting space, extracts the meeting URI from the API response, and emails teammates with a fixed subject and body template. That pattern fits standups, client calls, or internal demos when you live in the terminal and want agent-assisted scheduling without clicking through Google Calendar. Complexity is intermediate because you need Workspace credentials, prior gws skills, and comfort with JSON flags on CLI commands.15.3kinstalls67Recipe Share Folder With TeamRecipe Share Folder With Team is a short OpenClaw recipe in the Google Workspace CLI family that shares a Drive folder and its contents with named collaborators. You locate the folder with a Drive search query, create writer permissions for teammates who need to edit, reader permissions for stakeholders who only view, then list permissions in table form to confirm the ACLs stuck. Solo builders spinning up client or contractor access get a copy-paste command sequence instead of clicking through the Drive UI for every email. The recipe assumes you already load gws-drive and have a folder ID workflow after the search step. It is deliberately narrow: one folder, explicit roles, verifiable output—ideal when a spec or handoff doc lives in a shared tree and you want the agent to execute sharing consistently.15.3kinstalls68Recipe Create Expense Trackerrecipe-create-expense-tracker is a Google Workspace CLI recipe that walks an agent through creating an Expense Tracker spreadsheet, seeding Date/Category/Description/Amount columns, logging an initial travel line item, and sharing the file read-only with a manager. Solo founders and indie contractors who already use gws for Drive and Sheets can stand up bookkeeping in minutes instead of clicking through the Google UI or writing Apps Script. The recipe is procedural: each step is a copy-paste gws command with JSON payloads for file creation, range append, and permissions. It assumes you have loaded gws-sheets and gws-drive skills and the gws binary on PATH. Best treated as a starting template—you extend rows, formulas, and categories as your operate-phase finance habits evolve.15.3kinstalls69Recipe Sync Contacts To Sheetrecipe-sync-contacts-to-sheet is a Google Workspace CLI recipe skill that walks an agent through exporting domain directory contacts into Google Sheets. Solo builders and small teams use it when they need a living contact dump—names, emails, phones—for sales prep, onboarding audits, or lightweight CRM sync without writing a custom ETL. The workflow assumes you have already loaded gws-people and gws-sheets: first list people with gws people people listDirectoryPeople and a readMask, then seed a Contacts range with header row, then append one row per contact via gws sheets +append. It is intentionally procedural rather than a black-box integration, which makes it easy to adapt ranges, spreadsheet IDs, and pagination in follow-on runs. Best after Google Workspace access and gws auth are in place; not a substitute for full HRIS or marketing automation pipelines.15.3kinstalls70Recipe Review Meet Participantsrecipe-review-meet-participants is a short OpenClaw recipe for solo builders and small teams who already use Google Workspace CLI workflows. It walks through listing recent Google Meet conference records, enumerating participants for a chosen conference, and drilling into participant sessions so you can see attendance duration in table output. The skill explicitly requires loading gws-meet first and assumes the gws tool is installed. It does not create meetings or change Workspace settings—it only reads Meet conference APIs through documented gws subcommands. Best when you need a repeatable agent-driven audit after client calls, standups, or interviews rather than one-off manual reporting in the browser.15.3kinstalls71Persona Sales OpsPersona Sales Ops is an OpenClaw persona skill for indie founders and solo sellers who already live in Google Workspace and want their coding agent to behave like a lightweight sales coordinator. It does not replace a CRM; it orchestrates the gws CLI utilities for Gmail, Calendar, Sheets, and Drive around repeatable motions—prep for calls, log pipeline changes, turn follow-up mail into tasks, and publish proposals from Drive. The skill lists concrete workflow invocations such as meeting-prep, email-to-task, and weekly-digest so agents do not improvise OAuth or API steps. You should load the prerequisite gws-* skills first, keep client documents in a shared Drive folder, and schedule follow-ups right after meetings. It fits builders shipping B2B or services products who want agent-assisted pipeline hygiene without leaving Workspace.15.3kinstalls72Recipe Post Mortem Setuprecipe-post-mortem-setup is a Google Workspace CLI recipe skill for solo builders and small eng teams who already use the `gws` toolchain. It chains three focused skills—docs, calendar, and chat—into one procedural workflow: create a titled post-mortem Google Doc with a standard incident outline, schedule a one-hour review on Google Calendar with attendees, and ping the engineering space in Google Chat so nobody misses the retro. You load the prerequisite skills first, then run the documented commands with your incident title and timestamps substituted. The pattern fits operators who want repeatable incident hygiene without building custom integrations. It assumes Workspace admin or OAuth is already configured through the parent CLI skills, and it is best used right after severity is understood—not as a substitute for live triage or paging.15.3kinstalls73Persona Customer SupportPersona Customer Support is an OpenClaw persona skill for the Google Workspace CLI (`gws`). It tells your agent how to behave like a front-line support operator: triage labeled mail, turn messages into trackable tasks, mirror state in a spreadsheet, ping the team in Chat when something is urgent, and put customer calls on Calendar. Solo founders often wear this hat without a full Zendesk stack—this persona wires familiar Workspace surfaces into a repeatable ritual. You must load the listed utility skills first (`gws-gmail`, `gws-sheets`, `gws-chat`, `gws-calendar`) and have the `gws` binary available. Workflows referenced include `gws workflow +email-to-task` and `gws workflow +standup-report`, so the agent can connect inbox work to daily status. Tips in the skill encourage Gmail filters, auto-labeling, and table-formatted dashboards for quick reads. Version 0.22.5 in metadata; category persona in openclaw config.15.3kinstalls74Recipe Create Feedback Formrecipe-create-feedback-form is a Google Workspace CLI recipe that walks a solo builder through creating a feedback Google Form and sharing its link by email. You need the gws binary plus the gws-forms and gws-gmail skills loaded first. The flow creates the form with a JSON info block, pulls the responder URL from the API response, then sends a Gmail message with that URL in the body. It fits indie operators running events, betas, or customer check-ins who already use gws for Workspace automation and want a repeatable script instead of clicking through Forms and Gmail separately. Complexity is intermediate because OAuth, skill prerequisites, and JSON quoting must be correct.15.2kinstalls75Gws Modelarmorgws-modelarmor is an agent skill for solo builders who ship products that call Google generative APIs and need a repeatable safety layer. It documents how to drive Google Model Armor through the `gws` CLI: list resources, introspect methods, and invoke sanitize and template APIs with correctly typed flags. Companion helper skills cover sanitizing user prompts, sanitizing model responses, and creating new armor templates so you do not hand-roll REST payloads. You are expected to read the shared gws skill first for authentication, global flags, and security rules. The skill fits indie teams bolting guardrails onto chat features, internal copilots, or customer-facing agents without building a separate moderation microservice. It is an integration guide, not a hosted policy engine—your templates and GCP project still own enforcement.15.2kinstalls76Gws Modelarmor Create Templategws-modelarmor-create-template is a narrow Google Workspace CLI skill for solo builders shipping LLM features on GCP who need Model Armor policies in code, not console-only clicks. It walks the agent through gws modelarmor +create-template with project, region, and template id, defaulting to the jailbreak preset when neither preset nor JSON is supplied. The skill explicitly depends on gws-shared/SKILL.md for authentication, global flags, and security rules, and warns that template creation is a mutating operation requiring user confirmation. After creation, template names feed sanitize-prompt and sanitize-response commands for runtime filtering. Ideal when you are wiring agent backends or customer-facing chat and want a reproducible security baseline before launch. It is integration-shaped: one command family, explicit prerequisites, and caution callouts rather than a full threat-modeling methodology.15.1kinstalls77Recipe Share Event MaterialsRecipe Share Event Materials is a short OpenClaw-style agent recipe for solo builders and small teams who already use the Google Workspace CLI (gws). After you load the gws-calendar and gws-drive skills, it walks through fetching attendees from a primary-calendar event, granting each attendee reader access on a chosen Drive file via permissions.create, and confirming shares with permissions.list in table format. It fits when you routinely circulate decks or notes after calls and want repeatable shell commands instead of clicking Share in the UI. The skill does not replace OAuth setup or Drive folder governance—it assumes gws is installed and authenticated. Pair it with calendar and drive skills in the same repo before invoking this recipe.15.1kinstalls78Recipe Send Team Announcementrecipe-send-team-announcement is a thin workflow recipe for solo builders and tiny teams who already use the Google Workspace CLI. Instead of inventing a new integration, it sequences two established skills: send a detailed email with gws-gmail, then post a concise Chat notice with gws-chat so people in the space know to check inbox. The pattern mirrors how real announcements work—long form in email, nudge in chat. You must load gws-gmail and gws-chat before invoking this recipe. It is beginner-friendly because the steps are copy-paste commands with placeholders for team address and space ID. It does not replace drafting the message, choosing recipients, or compliance review; it only standardizes the dual-channel send path for agents following Prism-documented gws stacks.15.1kinstalls79Recipe Log Deal UpdateRecipe Log Deal Update is a focused gws CLI recipe for solo sellers who maintain a Sales Pipeline spreadsheet in Google Drive and want their agent to log outcomes consistently. The flow finds the pipeline file by name and spreadsheet MIME type, reads the existing Pipeline tab through column F, then appends a row with date, company, stage, deal size, quarter, and owner fields. It assumes you already use the gws tool chain and have loaded the Sheets and Drive utility skills named in the prerequisite block. Pair it with the Sales Ops persona for broader meeting and digest workflows, or invoke it alone right after a call when you only need a ledger update. The recipe is procedural command documentation—not a CRM—so column order and sheet naming must match the examples or be adapted in your fork.15kinstalls80Gws Modelarmor Sanitize PromptGws-modelarmor-sanitize-prompt wraps Google Cloud Model Armor’s sanitize-prompt operation for builders who already use the gws CLI in Google Workspace–aligned workflows. You point the command at a template such as projects/PROJECT/locations/LOCATION/templates/TEMPLATE, pass user text via --text, a JSON body, or stdin, and receive filtered prompt content suitable for downstream LLM calls. The skill stresses reading gws-shared/SKILL.md first for authentication and security rules, and notes the sibling sanitize-response path for outbound filtering. Solo builders shipping agents or SaaS features with user-generated prompts install it to add a consistent Google-managed safety gate instead of bespoke regex filters. It fits the Ship phase when hardening prompts prior to launch, especially when compliance or abuse prevention requires templated Model Armor policies rather than ad-hoc moderation.14.9kinstalls81Recipe Create Classroom CourseRecipe-create-classroom-course is a compact agent skill that turns Google Classroom setup into copy-paste gws CLI steps for solo educators, indie course creators, or builders automating school workflows. You create a course with structured JSON metadata, send a student invitation, and verify enrollment with a table-formatted student list. The recipe pattern assumes you already loaded the gws-classroom skill and have the gws binary available, so it is not a standalone OAuth tutorial. It suits builders who treat Classroom as another API surface in a larger automation repo rather than admins clicking only in the web UI. Expect course and invitation IDs to be threaded manually between steps until you wrap the recipe in your own scripts.14.9kinstalls82Gws Modelarmor Sanitize ResponseGWS Model Armor Sanitize Response is a Google Workspace CLI skill that runs Model Armor templates against model-generated text before end users see it. Solo builders shipping chatbots, copilots, or agent UIs invoke gws modelarmor +sanitize-response with a full template resource name and either --text or a JSON body, often piping command output through the CLI. The skill points to gws-shared for authentication and global flags and explicitly contrasts outbound sanitization with +sanitize-prompt for user-to-model inbound checks. It fits indie SaaS and API products that must align with Google Cloud safety policies without building a custom moderation stack from scratch.14.9kinstalls83Gws ClassroomGws-classroom is a Google Workspace CLI skill for solo builders and small teams who run coursework, cohorts, or training products on Google Classroom and want their coding agent to speak the API through the gws tool instead of hand-rolled REST calls. The skill documents the classroom v1 command shape and enumerates course-oriented methods including create, get, delete, and grading-related operations, with explicit permission and NOT_FOUND error semantics copied from the API. Before any command, the agent must read the sibling gws-shared skill for authentication, global flags, and security rules; if that file is missing, the docs point you to gws generate-skills to regenerate the shared layer. This is a tight integration skill: one binary, one API family, predictable flags. It fits builders automating roster sync, course provisioning from a repo, or admin scripts—not consumers who only use the Classroom web UI without CLI access.14.8kinstalls84Gws Scriptgws-script is an agent skill that wraps the Google Workspace CLI (`gws`) for Google Apps Script project management. Solo and indie builders use it when they automate Docs, Sheets, Gmail, or Chat with Apps Script but want agent-driven or scripted operations instead of only the browser editor. It covers creating projects, reading and updating script file content and manifests, inspecting script and user processes, and fetching execution metrics. The skill points to gws-script-push for uploading local sources. It assumes you have installed `gws`, completed auth per gws-shared, and understand that updated content becomes the HEAD version used by triggers, add-on preview, web apps, and API execution. Complexity is intermediate because OAuth, project IDs, and Apps Script deployment models still need human judgment.10.5kinstalls85Gws Script Pushgws-script-push is a Google Workspace CLI skill for indie builders automating Sheets, Docs, or internal workspace tools with Apps Script. After auth via the shared gws skill, you point the CLI at a Script Project ID and optionally a source folder; the push uploads every supported file and overwrites the remote project in one shot. That makes it the deploy step in a local-edit loop rather than the Apps Script web editor alone. Because the operation is destructive at the project-file level, the skill flags explicit user confirmation. Prerequisites are the gws binary, the gws-shared skill for credentials, and a known script ID. Ideal when your agent already generated or refactored script files locally and you need them live in Google’s runtime.10.3kinstalls