# Gbrain Advisor

Proactive "make the most of gbrain" coaching.

- Repository: https://github.com/garrytan/gbrain (31427 stars)
- Category: Engineering
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add garrytan/gbrain --skill gbrain-advisor -g -a claude-code -y`
Codex: `npx skills add garrytan/gbrain --skill gbrain-advisor -g -a codex -y`
Cursor: `npx skills add garrytan/gbrain --skill gbrain-advisor -g -a cursor -y`
Gemini CLI: `npx skills add garrytan/gbrain --skill gbrain-advisor -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add garrytan/gbrain`

## Description

Proactive "make the most of gbrain" coaching. Runs `gbrain advisor` on a cadence and pings the user with the top high-leverage actions for their brain: version drift, pending migrations, stalled jobs, low embed coverage, setup smells, and uninstalled brain skills. Read-only; always asks before fixing.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# gbrain Advisor

> **Convention:** See `skills/conventions/brain-first.md`. This skill is the
> proactive voice of the brain, it tells the owner how to run it better.

## Contract

This skill guarantees:
- **Read-only.** `gbrain advisor` never mutates. It computes a ranked list of
  actions from existing brain state.
- **Print, never execute.** You SHOW the user the findings and ASK before running
  any fix. The user owns every decision.
- **Bounded nagging.** On a cadence, surface only what changed or what's
  critical; don't repeat an ignored low-severity item every run.

## When to run

- On demand when the user asks "how do I get more out of this brain?"
- On a **weekly** cadence via the cron recipe below (even idle brains get a
  "here's how to run this better" ping).
- Monthly, the advisor also surfaces the backup-coverage verdict (`gbrain
  backup status`, which knowledge repos have no git remote); relay any warn.

## How to run it

```bash
gbrain advisor --json
```

Exit code is the severity gate (E2): `0` clean, `1` warn, `2` critical. The JSON
payload is `{ version, generated_at, worst, findings: [...] }`. Each finding has:

- `severity`, `critical` | `warn` | `info`
- `title`, one-line why-it-matters
- `fix.command_argv`, the exact command to fix it (a structured argv)
- `fix.dispatch_id`, present when the fix is safe to run via `--apply`

## What to do with the findings

1. Read the findings, highest severity first.
2. Summarize the top 1-3 to the user in their own channel/voice. Lead with any
   `critical` item (e.g. pending migrations).
3. For each, show the `fix.command_argv` and **ask** whether to run it.
4. If they say yes and the finding has a `fix.dispatch_id`, you may run it
   locally with an explicit confirm:

   ```bash
   gbrain advisor --apply <dispatch_id>
   ```

The rest: https://github.com/garrytan/gbrain/blob/HEAD/plugin-variants/gbrain-daily/skills/gbrain-advisor/SKILL.md