Slash Command

/setup

Verify the gcp-inspector connector's prerequisites and write its config. Idempotent.

Install

npx claudepluginhub abnejllc/grc --plugin gcp-inspector

Referenced Files

example.com

Prompt Preview

# /gcp-inspector:setup

Prepares the gcp-inspector connector. Confirms `gcloud` CLI is installed and authenticated, writes `~/.config/claude-grc/connectors/gcp-inspector.yaml`, and runs a read-only health check.

## How to run



Exits 0 on success, 2 on missing/invalid credentials, 5 on missing `gcloud` binary.

## Credential precedence

Honors the standard gcloud credential chain:

1. `--project` / `--region` flags (written to config)
2. `GOOGLE_APPLICATION_CREDENTIALS` env var pointing at a service-account JSON
3. `gcloud config get-value project` and `gcloud config get-value compute/reg...

Command Content

Other plugins with /setup

/setup

Initializes or resumes project setup via interactive Q&A, creating conductor/ artifacts for product definition, guidelines, tech stack, workflow, and style guides.

conductor

32.9k

/setup

Detects ghost or inconsistent claude-hud plugin installations (orphaned cache, stale registry, temp files) and offers cleanup on user confirmation for macOS/Linux/Windows.

BashReadEdit+1

claude-hud

20.8k

/setup

Checks local Codex CLI readiness, prompts to install if unavailable via npm, and optionally toggles stop-time review gate.

Bash(node:*)Bash(npm:*)AskUserQuestion

codex

11.4k

/setup

Guides enterprise admins through Claude Office add-in setup for Vertex AI, Bedrock, or custom gateway; provisions credentials and generates deployable manifest.xml.

claude-in-office

7.3k

/setup

commands/

Runs interactive setup wizard: detects AI providers (Codex, Gemini, Ollama, etc.), installs missing ones via Bash, configures auth, and sets up RTK token optimization.

BashReadGlob+2

octo

2.8k

/setup

Guides user through interactive onboarding wizard for Ouroboros setup.

ouroboros

2.7k

Stats

Parent Repo Stars0

Parent Repo Forks0

Last CommitApr 18, 2026

Used By2 plugins

Actions

View Source View Plugin View on GitHub View README

/gcp-inspector:setup

Prepares the gcp-inspector connector. Confirms gcloud CLI is installed and authenticated, writes ~/.config/claude-grc/connectors/gcp-inspector.yaml, and runs a read-only health check.

How to run

bash plugins/connectors/gcp-inspector/scripts/setup.sh [--project=<id>] [--region=<region>]

Exits 0 on success, 2 on missing/invalid credentials, 5 on missing gcloud binary.

Credential precedence

Honors the standard gcloud credential chain:

--project / --region flags (written to config)
GOOGLE_APPLICATION_CREDENTIALS env var pointing at a service-account JSON
gcloud config get-value project and gcloud config get-value compute/region
Application Default Credentials (ADC) via gcloud auth application-default login

The setup script runs gcloud auth list and gcloud projects describe to verify the resolved identity has access before writing the config.

What it does

Check gcloud CLI is installed (gcloud --version).
Resolve credentials (gcloud auth list --filter=status:ACTIVE).
Resolve project (from --project, CLOUDSDK_CORE_PROJECT, or gcloud config).
Verify the caller can at least gcloud projects describe the project (read IAM policy check).

Write config:

version: 1
source: gcp-inspector
source_version: "0.1.0"
project_id: "<project>"
project_number: "<number>"
caller: "<email-or-sa>"
default_region: "us-central1"
defaults:
  services: ["iam", "storage", "logging", "kms", "compute"]

Typical output

gcp-inspector:setup ✓
  gcloud:          557.0.0
  project:         acme-prod (number 1234567890)
  caller:          ethan@example.com
  default region:  us-central1
  config:          ~/.config/claude-grc/connectors/gcp-inspector.yaml

Next: /gcp-inspector:collect

Failure modes

gcloud not installed: exit 5. brew install --cask google-cloud-sdk or https://cloud.google.com/sdk/docs/install.
No active account: exit 2. Run gcloud auth login then gcloud auth application-default login.
Project not accessible: exit 2. Either the project doesn't exist or the caller lacks resourcemanager.projects.get. Required role: at minimum roles/viewer; for a full scan, roles/iam.securityReviewer + roles/cloudkms.viewer + roles/logging.viewer.

Safe to re-run

Yes. Overwrites config; preserves cached findings.