garrytan/gbrain

gbrain-advisor

Proactive "make the most of gbrain" coaching.

소스 보기

사용 방법

  1. 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
  2. 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
  3. 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/garrytan/gbrain --skill gbrain-advisor

시작 전 확인

  • 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
  • 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서

원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.

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

  1. For each, show the fix.command_argv and ask whether to run it.
  2. 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>

--apply is local-only, runs the fix as a structured argv (no shell), and confirms first. Findings without a dispatch_id are not auto-runnable — run their fix.command_argv yourself after the user agrees.

  1. Never run a fix the user didn't approve.

Cron recipe (weekly checkup)

Install a weekly job via the cron-scheduler skill. Keep the prompt THIN — the job just reads this skill and runs the advisor:

  • Schedule: weekly, one quiet-hours-respecting slot (e.g. Monday 09:00 local).
  • Job prompt: Read skills/gbrain-advisor/SKILL.md and run gbrain advisor --json. If anything is critical or new since last run, ping me with the top items and the exact fix commands. Ask before fixing.
  • Idempotent: the advisor is read-only, so a double-fire is harmless.

The advisor records a local run history, so on each fire you can tell the user what is new since last run rather than re-listing everything.

Output Format

When you surface advisor findings to the user, lead with severity and keep it scannable:

🧠 gbrain checkup — 2 things worth your attention

CRITICAL  Schema migrations are pending.
          Fix: gbrain apply-migrations --yes   (want me to run it?)

WARN      gbrain 0.44 is available (you're on 0.43).
          Fix: gbrain upgrade
  • One block per finding, highest severity first.
  • Always show the exact fix command and ASK before running it.
  • If nothing is pressing, say so in one line ("brain looks healthy") — don't

manufacture work.

When it fails

Follow the agent operator protocol for any gbrain error code, exit code, [AGENT] block or notice block. Specific to this skill:

  • A critical finding (pending migrations) carries a fix such as gbrain apply-migrations --yes: ask the user before running it; findings without a dispatch_id are not auto-runnable.
  • gbrain advisor cannot reach the brain (GBRAIN_DB_ACCESS marker): route to the db-repair skill instead of reporting "no findings".

Anti-Patterns

  • Running a fix without asking. The advisor is read-only by contract. Never

run --apply (or any fix command) without the user's explicit yes.

  • Dumping the raw JSON at the user. Translate findings into their voice; lead

with what matters.

  • Re-nagging ignored low-severity items every run. Use the "new since last

run" delta; respect the user's prior non-action.

  • Treating `info` like `critical`. Only block/insist on critical findings

(pending migrations). info is a gentle nudge.

  • Calling the MCP `advisor` op for workspace install state. Over MCP the

advisor returns brain-state signals only; uninstalled-skill findings are a local-CLI concern.

같은 저장소의 Skills

더 많은 Skills

모든 Skills
garrytan
커뮤니티

academic-verify

Verify a research claim or academic citation by tracing it through publication → methodology → raw data → independent replication. Routes through perplexity-research for the actual web lookup, then formats results as a citation-checked brain page. Use when a book/article/conversation cites a study and you want to confirm the claim is real, replicated, and accurately characterized.

1시간 설치 수
1
GitHub Stars
3.3만
업데이트
11월 11일
garrytan
커뮤니티

ask-user

Reusable pattern for presenting the user with explicit choices and gating execution until they respond. Used by other skills when a decision point requires human input before proceeding. Platform-agnostic — works on Telegram (inline buttons), Discord, CLI, or any agent with a message tool.

1시간 설치 수
1
GitHub Stars
3.3만
업데이트
11월 11일
garrytan
커뮤니티

brain-ingest-gate

Pre-write quality gate for content entering the brain. No raw copies: a bare cp/mv into the brain repo is a bug. Before any new page lands, resolve named entities registry-first (a vector score is a floor for prose, never a gate for named things), then run the read-the-top-hit dedup decision tree (clear-dup / plausible-dup / clear). Owns dedup; delegates enrichment to the shipped ingestion skills. Routing convention, not an operation-boundary enforcement.

1시간 설치 수
1
GitHub Stars
3.3만
업데이트
11월 11일
garrytan
커뮤니티

brain-ops

Brain knowledge base operations. The core read/write cycle: brain-first lookup, read-enrich-write loop, source attribution, ambient enrichment, back-linking. Read this before any brain interaction.

1시간 설치 수
1
GitHub Stars
3.3만
업데이트
11월 11일