Menu

Individual skill

gsuite-setup

0upvotes

Configure or audit Google Workspace (formerly G Suite) organization settings for open collaboration, user autonomy, external sharing, Groups privacy, Gmail delegation, Calendar, Meet, Chat, Drive, Directory, and profile editing. Use for new Workspace setup, restrictive-default cleanup, onboarding a small collaborative organization, or verifying that the Latent Space openness baseline remains applied.

gsuite-setup/SKILL.md

Read pinned source

Source commit 1acf58f08cca24b764a4352a6c30fed1f7fb9fb6

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 7, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
198
Repository last updated
Nov 9, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# G Suite Setup

Configure Google Workspace through the authenticated Admin Console while changing only settings that differ from the requested baseline.

## Required workflow

1. Use the user's authenticated Chrome session. If Chrome automation is blocked by browser UI, use the Computer Use skill to dismiss or work around the obstruction without leaving Chrome.
2. Verify the active Google account, organization, and organizational unit before editing. For Latent Space, target the root `Latent Space` organizational unit unless the user specifies a narrower scope.
3. Read [references/openness-baseline.md](references/openness-baseline.md) before auditing or applying the baseline.
4. Inspect each relevant setting before editing. Skip settings already matching the baseline and report them separately from actual changes.
5. Apply one coherent product area at a time and wait for Google's saved confirmation before moving on.
6. Re-open or re-snapshot changed sections to verify the persisted state. Treat propagation notices as pending, not proof of immediate user-visible behavior.
7. Report three categories: changed, already correct, and unavailable or per-user-only.
Back to top