Setup & Installation
Or with the ClawHub CLI, for registry-managed skill folders outside a full OpenClaw workspace:
Version History
- Added explicit author field with contact information in the skill metadata. - Updated metadata formatting for improved readability and YAML structure. - No changes to core functionality or usage instructions.
What This Skill Does
Bridle is a CLI for managing configurations across AI coding assistants. Create named profiles, install skills and agents from GitHub repos, and switch between setups for Claude Code, OpenCode, Goose, and Amp without manually editing config files.
Each AI coding assistant stores config in a different location and format; bridle provides one CLI to manage all of them consistently.
When to use it
- Switching Claude Code from a minimal profile to a full work setup with MCPs
- Installing a skill from a GitHub repo into multiple AI assistants at once
- Comparing two Claude Code profiles before deciding which to activate
- Keeping separate personal and client-specific configurations per tool
- Checking which profile is active across all AI assistants from one command
Example Workflow
Here's how your AI assistant might use this skill in practice.
User asks: Save my current Claude Code setup as a work profile and switch to it
- 1Runs `bridle profile create claude work --from-current` to snapshot the current config
- 2Confirms the profile with `bridle profile show claude work`
- 3Runs `bridle profile switch claude work` to activate it
- 4Runs `bridle status` to verify the active profile across all harnesses
Claude Code is now running under the 'work' profile with the saved configuration
Requirements
Accounts, API keys, or tools you or your AI assistant may need to set up while using this skill.