setup-brain

Configure Team-Brain templates by managing repository manifests and lifecycle namespaces.

3|Updated Apr 27, 2026

Search Tags:#automation #template #onboarding #configuration #wiki #agent-workflow

Ready to run

npx skills add https://github.com/zoraxl/team-brain --skill setup-brain-zoraxl

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: setup-brain
Source: https://github.com/zoraxl/team-brain/tree/main/.cursor/skills/setup-brain
Command: npx skills add https://github.com/zoraxl/team-brain --skill setup-brain-zoraxl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates the friction of manually configuring a new team wiki or migrating existing documentation into the Team-Brain structure, ensuring a consistent and functional knowledge base from day one.

Core Features & Use Cases

Automated Onboarding: Guides users through configuring repos.yaml, namespaces, and zones for both new and existing brains.
Surface Synchronization: Automatically detects and mirrors skill sets across agent tools like Claude Code, Cursor, and Codex.
Health Checks: Provides a re-runnable diagnostic tool to verify configuration status and identify missing setup steps.

Quick Start

Run the setup-brain skill to configure this repository as a new team brain and install the necessary agent tools.

Frequently Asked Questions about setup-brain

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate team wiki onboarding and documentation migration into a consistent structure?▼

Automating team wiki onboarding involves configuring repository manifests, lifecycle namespaces, and agent-specific skill mirrors to ensure structural consistency across new template clones and existing documentation migrations.

How does skill mirroring work across agent tools like Claude Code, Cursor, and Codex?▼

Skill mirroring works by automatically detecting and synchronizing skill sets across agent tools like Claude Code, Cursor, and Codex, ensuring surfaces remain consistent without manual configuration for each specific environment.

Can I use this setup to configure repos.yaml and namespaces for an existing team brain?▼

Yes, you can use this setup to configure repos.yaml and namespaces for existing brains, as it operates across both new template clones and existing documentation migrations to maintain structural consistency.

Do I need local file system access and shell commands to validate configuration state?▼

Yes, local file system access and shell commands are required to validate configuration state, synchronize skill directories, and ensure the team brain template is properly configured and functional.

Why does my team brain configuration setup show missing steps after migration?▼

Missing steps after migration indicate incomplete configuration state, which can be identified by running a re-runnable diagnostic health check to verify configuration status and pinpoint exactly what remains unconfigured.