Managing Skills

Configuring skillsets

Installing skills requires at least one configured skillset. Gamut ships with a default public skillset; add more from settings:

1. Open Settings and go to the Skillsets tab.
2. Enter the skillset's Git repository URL (HTTPS or SSH).
3. Click Add. Gamut validates the repository by cloning it and checking for a valid index.json.

Added skillsets appear in the list with their name, description, and skill count. Skills from every configured skillset are available for installation across all agents.

Private GitHub repositories require SSH authentication. Gamut clones with GIT_TERMINAL_PROMPT disabled, so interactive password prompts are not supported.

Platform skillsets

Skillsets published by a connected platform organization sync automatically. They appear in the list with a "Platform" badge and need no manual URL entry.

Refreshing a skillset

Click the refresh button next to a skillset to pull the latest changes from the remote repository. New skills and version changes become visible after the refresh.

Removing a skillset

Click the delete button to remove a skillset from the configuration and clean up its local cache. Skills already installed into agents are unaffected and stay in the agent's workspace.

Browsing skills

Each agent has a Skills section on its home page. When configured skillsets contain skills the agent does not yet have installed, an Add Skill button appears.

The browse dialog supports:

• Search: match skills by name or description.
• Filter: narrow to a single skillset when several are configured.
• Pagination: page through large catalogs.

Each skill card shows the skill's name, source skillset, and version.

Installing a skill

Click the install button on a skill's card. Gamut copies the skill's files from the skillset cache into the agent's workspace at .claude/skills/<skill-name>/.

Required environment variables

Some skills declare required environment variables in their SKILL.md frontmatter, typically API keys or configuration values needed at runtime:

---
name: Database Query
description: Queries a PostgreSQL database and returns formatted results.
metadata:
  version: 1.0.0
  required_env_vars:
    - name: DATABASE_URL
      description: PostgreSQL connection string
    - name: DB_READ_ONLY_TOKEN
      description: Read-only access token for the database
---

Installing such a skill opens a dialog prompting for each value. The values are stored as agent secrets and made available during execution. All required variables must be provided before the install completes.

Skill status

Every installed skill shows a status badge. Gamut computes it by comparing the installed skill's content hash against the original install and the latest version in the skillset cache.

• Up to date: the skill matches the version in the skillset repository.
• Update available: the skillset contains a newer version, either a version bump in index.json or changed file content. An Update button appears on the card.
• Locally modified: the skill's files have been edited (by you or the agent) since install, so the SHA-256 hash no longer matches the one recorded at install time. Either submit the changes upstream or Force sync to discard them and restore the latest skillset version. Force sync cannot be undone.
• Local: the skill was created locally and has no upstream tracking. Publish it to make it available to others.

Updating skills

Gamut checks for updates automatically when an agent is opened, pulling the latest changes from all configured skillsets in the background. Clicking Update re-fetches the skillset, copies the latest files into the agent's workspace, and records the new version and content hash.

Exporting and importing skills

Skills can move between agents and machines without going through a skillset:

• Export: save an installed skill as a ZIP archive.
• Import: add a skill to an agent from a ZIP archive.
• Double-click: opening a .skill file imports the skill into Gamut; .agent files import an agent the same way.

Publishing and submitting changes

Locally modified skills can be contributed back to their skillset. The workflow depends on the provider.

GitHub skillsets

1. Click Open PR on a locally modified skill.
2. Gamut generates a suggested title, description, and version bump from the diff.
3. Review and edit the suggestions, then confirm.
4. Gamut forks the repository (if needed), creates a branch, commits the changes, and opens a pull request against the upstream repository.

This requires the GitHub CLI (gh) to be installed and authenticated.

Platform skillsets

1. Click Submit on a locally modified skill.
2. Review the suggested title and description.
3. Gamut submits the changes to the platform's review queue.
4. The submission is tracked in the skill's metadata. Once the platform merges or rejects it, the status updates on the next refresh.

Publishing a local skill

1. Click the publish button on the local skill's card.
2. Select the target skillset.
3. Review the generated title, description, and version.
4. Confirm to submit.

The skill is added to the skillset's index.json and placed under skills/<skill-name>/ in the repository.

Removing a skill

Delete the skill's directory from the agent's workspace. Removal affects only that agent; other agents with the same skill, and the skillset repository itself, are untouched.