agentleFS
omnipresence-osomnipresence-os/claude-skills/disconnect-google-cloud/SKILL.md

disconnect-google-cloud

Skill0 starsChanged 6 months agoLicence not identifiedView on GitHub

Removes the user's Google Cloud credentials (service account JSON and/or OAuth refresh token) from their machine. Trigger when the user says any of "disconnect google", "disconnect google cloud", "remove google credentials", "delete google service account", "unhook google", "remove google cloud key", "tear down google connection", "remove GSC connection", "remove GA4 connection", "disconnect drive". Removes ~/.claude/.omni-google-sa.json and/or ~/.claude/.omni-google-oauth.json — after which Omni can no longer access any Google service (GSC, GA4, Drive, Docs, Sheets) until they re-run `connect google cloud`. Confirms with the user before deleting. Reminds them that local removal does NOT revoke the credential globally — to fully invalidate, they must also delete the service account key (or OAuth client) in the Google Cloud console. To rotate just the credential, re-run `connect google cloud` instead — it's idempotent.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    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
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.