What problem does it solve? Setting up a persistent, searchable knowledge base for a coding agent involves many fragile steps: installing the gbrain CLI, choosing and initializing a storage engine (local PGLite, Supabase Postgres, or a remote MCP server), registering MCP tools, and capturing per-repo trust policies. This Skill automates that entire onboarding flow with idempotent, rollback-safe steps. ## Core Features & Use Cases - Multi-path engine setup: Initialize gbrain against an existing Supabase URL, auto-provision a new Supabase project, run a local PGLite database, or connect to a remote gbrain MCP server over HTTP with a bearer token. - Broken-engine remediation: Detects dead or misconfigured engines and offers retry, rollback-safe switch to PGLite, or full re-initialization. - Transcript and memory ingest: Optionally ingests Claude Code, Codex CLI, and Cursor session transcripts plus curated gstack artifacts into gbrain, with per-remote trust policies (deny/read-only/read-write) and optional gitleaks secret scanning. - Use Case: A developer on a new machine runs the setup once and gets gbrain installed, MCP-registered in Claude Code, transcripts indexed, and a GBrain Configuration block persisted to CLAUDE.md so future sessions auto-load prior context. ## Quick Start Ask the agent to set up gbrain on this machine, for example: "Run /setup-gbrain to install gbrain, initialize a local PGLite brain, and register it as an MCP server."