setup

Install BRAINS dependencies, configure multi-LLM providers, and set global or local defaults.

2|1|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/Epiphytic/brains --skill setup-epiphytic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: setup
Source: https://github.com/Epiphytic/brains/tree/main/skills/setup
Command: npx skills add https://github.com/Epiphytic/brains --skill setup-epiphytic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines the initial BRAINS setup by guiding dependencies installation, provider configuration, and default-mode settings for each skill.

Core Features & Use Cases

  • Global and Local Setup: installs tools, validates versions, and writes global defaults or per-project overrides.
  • Provider Configuration: configures Star-Chamber providers for multi-LLM workflows and saves them for reuse.
  • Project Bootstrapping: creates project-specific files and directories to store local BRAINS settings and docs.

Quick Start

Run /brains:setup --global to install dependencies, configure providers, and set defaults, or /brains:setup --local for a per-project setup.

Frequently Asked Questions about setup

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

FAQPage Schema
How do I configure multi-LLM providers for my project?

Configure multi-LLM providers by running the setup command, which installs dependencies and saves Star-Chamber provider configurations for reuse across global or project-specific workflows.

What is the best way to install dependencies and set defaults for a new project?

Run a local setup command to install dependencies, validate versions, and write per-project default overrides, bootstrapping project-specific files and directories for local settings.

Can I set up configuration globally across my system or just locally?

Yes, you can configure both globally and locally. Global setup writes system-wide defaults, while local setup creates project-specific files and directories to store per-project overrides.

Does the setup process validate dependency versions before writing defaults?

Yes, the setup process validates dependency versions during installation. It streamlines initial configuration by guiding dependency installation and applying default-mode settings for each skill.

Why do I need to configure Star-Chamber providers for multi-LLM workflows?

Configuring Star-Chamber providers is needed to enable multi-LLM workflows. The setup process configures these providers and saves them for reuse, streamlining your initial configuration.