connect-google-cloud
Skill0 starsChanged 6 months agoLicence not identifiedView on GitHub
Walks the user through setting up Google Cloud credentials so Omnipresence can access their Google Search Console, Google Analytics 4, Drive, Docs, Sheets, and other Google APIs. Trigger when the user says any of "connect google", "connect google cloud", "set up GSC", "set up search console", "connect search console", "connect GA4", "connect google analytics", "connect drive", "connect google drive", "set up google", "wire up google APIs", "set up google service account", "I want omni to access my GSC / GA4 / Drive / Docs / Sheets". This is the ONE canonical Google Cloud credential setup. Two paths: service account (recommended for resources the user admins) and OAuth (fallback for granted-user-only resources). The flow is incremental — set up ONE integration, test it live, then move on — so users get a fast feedback loop instead of finding setup is broken after a 20-minute click marathon. OAuth path uses a local-server flow (browser opens, user signs in, refresh token captured automatically) — NOT the OAuth Playground, which testing showed members find overwhelming. Key file handling is path-based — user provides the file path to the downloaded JSON, agent reads from disk and moves into place, key contents never enter the chat transcript. Saves credentials locally to ~/.claude/.omni-google-sa.json and/or ~/.claude/.omni-google-oauth.json. Idempotent — safe to re-run to add more integrations, refresh an expired OAuth token, or rotate credentials.
- Installs packages
In this repository23 other files it gives its agents.
- connect-dataforseoSkill
- connect-emailSkill
- connect-openaiSkill
- continue-strategySkill
- create-workerSkill
- disconnect-dataforseoSkill
- disconnect-emailSkill
- disconnect-google-cloudSkill
- disconnect-openaiSkill
- domain-migration-checklistSkill
- fill-project-gapSkill
- getting-startedSkill
- list-projectsSkill
- list-strategiesSkill
- load-workerSkill
- new-projectSkill
- new-strategySkill
- project-infoSkill
- project-resolverSkill
- push-changesSkill
- reload-workerSkill
- switch-projectSkill
- sync-omnipresenceSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
33 rules. About 0 are common, 24 are distinctive, and 9 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈24
Distinctive · estimate
This author's own choices. Worth a look.
9
Very specific
Tied to their project's names, files or tools. Probably skip.
The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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.
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
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.

