bridle
Unified configuration manager for AI coding assistants. Manage profiles, install skills/agents/commands, and switch configurations across Claude Code, OpenCode, Goose, and Amp.
What this skill does
# Bridle Skill Unified configuration manager for AI coding assistants. Manage profiles, install skills/agents/commands, and switch configurations across Claude Code, OpenCode, Goose, and Amp. ## Installation ```bash # Homebrew (macOS/Linux) brew install neiii/bridle/bridle # Cargo (Rust) cargo install bridle # From source git clone https://github.com/neiii/bridle && cd bridle && cargo install --path . ``` ## Core Concepts - **Harnesses**: AI coding assistants (`claude`, `opencode`, `goose`, `amp`) - **Profiles**: Saved configurations per harness (e.g., `work`, `personal`, `minimal`) ## Quick Commands ```bash # Launch interactive TUI bridle # Show active profiles across all harnesses bridle status # Initialize bridle config and default profiles bridle init ``` ## Profile Management ```bash # List all profiles for a harness bridle profile list <harness> # Show profile details (model, MCPs, plugins) bridle profile show <harness> <name> # Create empty profile bridle profile create <harness> <name> # Create profile from current config bridle profile create <harness> <name> --from-current # Switch/activate a profile bridle profile switch <harness> <name> # Open profile in editor bridle profile edit <harness> <name> # Compare profiles bridle profile diff <harness> <name> [other] # Delete a profile bridle profile delete <harness> <name> ``` ## Installing Components Bridle can install skills, agents, commands, and MCPs from GitHub repos and auto-translates paths/configs for each harness. ```bash # Install from GitHub (owner/repo or full URL) bridle install owner/repo # Overwrite existing installations bridle install owner/repo --force # Interactively remove components [experimental] bridle uninstall <harness> <profile> ``` ## Configuration Config location: `~/.config/bridle/config.toml` ```bash # Get a config value bridle config get <key> # Set a config value bridle config set <key> <value> ``` **Config keys:** `profile_marker`, `editor`, `tui.view`, `default_harness` ## Output Formats All commands support `-o, --output <format>`: - `text` (default) — Human-readable - `json` — Machine-readable - `auto` — Text for TTY, JSON for pipes ## Supported Harnesses & Config Locations | Harness | Config Location | Status | | ----------- | ----------------------- | ------------ | | Claude Code | `~/.claude/` | Full support | | OpenCode | `~/.config/opencode/` | Full support | | Goose | `~/.config/goose/` | Full support | | Amp | `~/.amp/` | Experimental | ## Component Paths by Harness | Component | Claude Code | OpenCode | Goose | | --------- | ----------- | -------- | ----- | | Skills | `~/.claude/skills/` | `~/.config/opencode/skill/` | `~/.config/goose/skills/` | | Agents | `~/.claude/plugins/*/agents/` | `~/.config/opencode/agent/` | — | | Commands | `~/.claude/plugins/*/commands/` | `~/.config/opencode/command/` | — | | MCPs | `~/.claude/.mcp.json` | `opencode.jsonc` | `config.yaml` | ## Common Workflows ### Create a work profile from current config ```bash bridle profile create claude work --from-current ``` ### Create profile from existing profile (duplicate & modify) ```bash # 1. Switch to the source profile bridle profile switch opencode default # 2. Create new profile from current (now the source profile) bridle profile create opencode minimal --from-current # 3. Edit the new profile to remove/modify as needed bridle profile edit opencode minimal ``` ### Switch between profiles ```bash bridle profile switch claude personal bridle profile switch opencode minimal ``` ### Check status across all harnesses ```bash bridle status ```
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.