Agent skill
bridle
Unified configuration manager for AI coding assistants. Manage profiles, install skills/agents/commands, and switch configurations across Claude Code, OpenCode, Goose, and Amp.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/data/bridle
Metadata
Additional technical details for this skill
- clawdbot
-
{ "os": [ "darwin", "linux" ], "emoji": "\ud83d\udc34", "install": [ { "id": "brew", "bins": [ "bridle" ], "kind": "brew", "label": "Install bridle via Homebrew", "formula": "neiii/bridle/bridle" }, { "id": "cargo", "bins": [ "bridle" ], "kind": "shell", "label": "Install bridle via Cargo", "command": "cargo install bridle" } ], "requires": { "bins": [ "bridle" ] } }
SKILL.md
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
# 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
# Launch interactive TUI
bridle
# Show active profiles across all harnesses
bridle status
# Initialize bridle config and default profiles
bridle init
Profile Management
# 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.
# 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
# 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-readablejson— Machine-readableauto— 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
bridle profile create claude work --from-current
Create profile from existing profile (duplicate & modify)
# 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
bridle profile switch claude personal
bridle profile switch opencode minimal
Check status across all harnesses
bridle status
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?