Search and write a shared company knowledge brain via the gbrain CLI.
npx skills add https://github.com/AMC-JTC/gbrain-1 --skill gbrain-amc-jtc
Please help me install this Agent Skill. Skill: gbrain Source: https://github.com/AMC-JTC/gbrain-1/tree/main/docs/integrations/qm-harness-snippets Command: npx skills add https://github.com/AMC-JTC/gbrain-1 --skill gbrain-amc-jtc
gbrain search, gbrain get, and gbrain query --json to answer questions about people, projects, decisions, and history with server-side read isolation. - Write-fenced durable memory: Persist conclusions with gbrain put under your own emp-<slug>/ and chan-<channel>/ slug prefixes, and cross-reference pages with gbrain link. - Roster-driven provisioning: The included provision-scopes.sh script registers one OAuth client per employee, converges write fences to the roster, and flags offboarded credentials for revocation. - Use Case: Before answering "who decided our database choice and why", run gbrain search to pull the decision page, then write new findings back to chan-eng/decisions/ so the whole team can find them. ## Quick Start Ask the agent to search the company brain for who decided a specific technical choice and why before answering the question.High-intent search queries and answers about installing and using this skill.
Run `gbrain search "your question"` for hybrid semantic plus keyword search, or `gbrain query "question" --json` for agent-tuned output. Use `gbrain get <slug>` to read a single page directly.
Use `gbrain put <slug> --content "..."` under your own write-fenced prefixes such as `emp-<your-slug>/` or `chan-<channel>/`. Writes outside your bound slug prefixes are rejected server-side.
Run `gbrain init --mcp-only` with the issuer URL, MCP URL, client ID, and client secret from the secret handoff, passing the secret via `--oauth-client-secret` so it persists to config. Verify with `gbrain whoami` before other commands.
This happens when the secret was passed via the GBRAIN_REMOTE_CLIENT_SECRET environment variable, which is deliberately not written to the config file. Re-run init with `--oauth-client-secret` so the credential persists on disk.
No. `gbrain remote doctor` requires admin scope, which per-employee clients do not have by design. Use `gbrain whoami` as the read-scope health check instead.
Use the included provision-scopes.sh script with a roster file listing channels and employees. It registers one OAuth client per employee with write fences, rescopes existing clients on re-runs, and flags offboarded credentials for revocation.
garrytanSearch and write a shared company knowledge brain via the gbrain CLI.
GregM1991Generates a Markdown discovery questionnaire for a recipient who holds knowledge the user lacks.
led8Manage task-scoped memory sessions and structured memory layers via a Neo4j-backed CLI.
KarlinskySStore and search vector embeddings with metadata filtering via Python and JavaScript APIs.