gws persona: Project Manager
Ready-to-use role playbook — relevant workflows, concrete instructions and tips for operating an agent as a project manager on Workspace
- What
- Ready-to-use role playbook — relevant workflows, concrete instructions and tips for operating an agent as a project manager on Workspace
- Cost
- Free
- Needs
- the `gws` binary on the PATH (see the repo README for install options); a Google account (browser OAuth via `gws auth login`, interactive and free); the `gws-shared` prerequisite skill installed first (the persona also cites gws-drive, gws-sheets, gws-calendar, gws-gmail and gws-chat — same repo, not listed in this catalog)
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
💳 Curated by Skill Harbor — the Project Manager persona: a role playbook that tells an agent how to operate as a PM on Google Workspace — relevant workflows (`+standup-report`, `+weekly-digest`, `+file-announce`), concrete instructions (track status in Sheets with `gws sheets +append`, share artifacts via Drive then `+file-announce`, schedule standups with `gws calendar +insert`, send status emails with `gws gmail +send`) and practical tips (jq piping, `--dry-run` before writes). Distinct from the lot 31 personas (`persona-researcher`, `persona-exec-assistant` — different roles, different instructions). By @googleworkspace, listed here with credit to its creator. Honest caveats: requires the `gws` binary and a Google account (browser OAuth is free); the cited `gws-drive`, `gws-sheets`, `gws-gmail`, `gws-calendar`, `gws-chat` prerequisite skills come from the same repo but are not listed in this catalog; install the prerequisite `googleworkspace-cli-gws-shared` first. Skill Harbor never reviews the code, review it yourself before use.
Version:
Quick answer
gws persona: Project Manager is a playbook from @googleworkspace for operating as a PM on Google Workspace, with standup-report and file-announce, track status in Sheets with gws sheets +append, share via Drive then +file-announce, schedule standups with gws calendar, and send status emails with gws gmail, plus jq piping and dry-run before writes. It requires gws and a Google account.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit a3768d0Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: the `gws` binary on the PATH (see the repo README for install options); a Google account (browser OAuth via `gws auth login`, interactive and free); the `gws-shared` prerequisite skill installed first (the persona also cites gws-drive, gws-sheets, gws-calendar, gws-gmail and gws-chat — same repo, not listed in this catalog) Install "gws persona: Project Manager" for me. Give my agent the Project Manager role playbook — relevant workflows, concrete instructions for tracking, sharing and scheduling on Google Workspace, and practical tips (jq piping, --dry-run before writes) Repository: https://raw.githubusercontent.com/googleworkspace/cli/a3768d0e82ad83cca2da97724e46bea4ff0e6dbd/skills/persona-project-manager/SKILL.md Pinned version: install the code at commit a3768d0e82ad83cca2da97724e46bea4ff0e6dbd exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file for the googleworkspace-cli-persona-project-manager skill from the repository into a temporary folder 2. Safety check: review the SKILL.md 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 into the agent's skills directory, in a folder named "googleworkspace-cli-persona-project-manager". 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. install the gws binary, run `gws auth login`). 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.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- a3768d0 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026 · Observed during the install test: registry.npmjs.org
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill 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 skill before installing it.