gaal.yaml file.
If you use Claude Code at work, Cursor at home, and try Codex on the side, your skills and MCP servers usually live in three places, .claude/, .cursor/, ~/.codex/, drifting out of sync the moment you set up a new machine. gaal fixes that. You write one file, run gaal sync, and every installed agent gets the same tools.
What gaal manages
| Resource | What it does |
|---|---|
| Repositories | Clones or updates Git, Mercurial, Subversion, Bazaar, tar, and zip sources into your workspace. |
| Skills | Installs SKILL.md collections into each agent’s native skills directory (.claude/skills, .cursor/skills, .github/skills, …). |
| MCP servers | Upserts MCP server entries into each agent’s JSON config file without touching your other settings. |
What it looks like
gaal.yaml
Who it’s for
- Solo developers running multiple coding agents who want their setup reproducible across machines via dotfiles.
- Power users maintaining curated skill sets across projects and teams.
- Anyone tired of copy-pasting MCP JSON snippets between agents.
What’s next
Install gaal
Five ways to get the binary on your machine.
Quickstart
Audit, init, and sync in five minutes.
How gaal works
The mental model: YAML → renderers → agent files.
The gaal.yaml file
Top-level keys and how they fit together.
What’s next for gaal
gaal today is the free, single-user CLI documented on this site. A team-focused Community Edition with shared registries, drift detection, and approval workflows is in development. Seegaal migrate for the graduation path.