Pinning repositories
Theversion: field accepts the right pin format for each VCS type:
Pinning skill sources
Skill sources don’t have aversion: field, they always track the source’s default branch. Two ways to pin:
1. Mirror the source as a repository, then point at it locally
2. Use a tag-pinned tarball
Pinning MCP servers
MCP entries writteninline: are pinned by definition, the command and arguments you wrote are exactly what runs:
npx-launched servers, pin the package version in the args (@1.4.0). For uvx, use uvx package==1.4.0. For binaries, point at a specific path.
When using source: to pull a remote MCP config, host the JSON yourself or pin to a tagged URL, never trust an HTTPS URL whose contents can change.
Reading current pins
gaal status reports the actual revision present on disk.