Configuration

Kasetto looks for kasetto.yaml in the current directory by default. Point it at a specific file or URL with --config, or run kst init to generate a starter.

Example

# Choose an agent preset (single or multiple)...
agent: codex
# agent:
#   - claude-code
#   - cursor

# ...or set an explicit path (overrides agent)
# destination: ./my-skills

# Install scope: "global" (default) or "project"
# scope: project

skills:
  # Pull specific skills from a GitHub repo
  - source: https://github.com/org/skill-pack
    branch: main
    skills:
      - code-reviewer
      - name: design-system

  # Sync everything from a local folder
  - source: ~/Development/my-skills
    skills: "*"

  # Pin to a specific git tag
  - source: https://github.com/acme/monorepo
    ref: v1.2.0
    skills:
      - name: custom-skill
        path: tools/skills

# MCP servers (optional)
mcps:
  - source: https://github.com/org/mcp-pack
  - source: https://github.com/org/monorepo
    path: mcps/my-server/pack.json

Reference

Top-Level Fields

Key	Required	Description
`agent`	no	One or more supported agent presets - string or list
`destination`	no	Explicit install path - overrides `agent` if both are set
`scope`	no	`"global"` (default) or `"project"` - where to install
`skills`	yes	List of skill sources
`mcps`	no	List of MCP server sources

Skill Source Fields

Key	Required	Description
`source`	yes	Git host URL or local path (GitHub, GitLab, Bitbucket, Codeberg/Gitea)
`branch`	no	Branch for remote sources (default: `main`, falls back to `master`)
`ref`	no	Git tag, commit SHA, or ref - takes priority over `branch`
`skills`	yes	`"*"` for all, or a list of names / `{ name, path }` objects

Skill Entry Fields

Each entry in the skills list can be a string (the skill name) or an object:

Key	Required	Description
`name`	yes	Name of the skill directory to install
`path`	no	Custom subdirectory within the source to look for the skill

MCP Source Fields

Key	Required	Description
`source`	yes	Git host URL or local path containing MCP server config
`branch`	no	Branch for remote sources (default: `main`, falls back to `master`)
`ref`	no	Git tag, commit SHA, or ref - takes priority over `branch`
`path`	no	Explicit path to the MCP JSON file within the source (skips auto-discovery)

Kasetto discovers MCP config files automatically in this order:

.mcp.json at the source root
mcp.json at the source root
Any .json file inside a mcp/ subdirectory

Use the path field to point at a specific file when the source contains multiple configs or uses a non-standard layout.

MCP config files must contain a mcpServers object with server definitions. Servers are merged into each agent's native settings file (e.g., .claude.json for Claude Code, .cursor/mcp.json for Cursor). See how sync works for merge behavior details.

Remote Configs

Kasetto can fetch configs from any HTTPS URL:

kst sync --config https://example.com/team-skills.yaml

Great for sharing a single config across a team without checking it into every repository.

If the URL points to a private repo, Kasetto uses the same token-based authentication as skill sources. See authentication for the full list of supported environment variables.

Multiple Agents

The agent field accepts a single value or a list. With a list, Kasetto installs skills to every agent's directory and merges MCP servers into every agent's settings file:

agent:
  - claude-code
  - cursor
  - codex

skills:
  - source: https://github.com/org/skill-pack
    skills: "*"

Handy when you juggle multiple agents and want them all to share the same skill set.

Agent vs Destination

If you set both, destination wins. Use agent for convenience with supported presets, or destination when you need full control over the install path.

Tip

Use destination when targeting an agent that isn't in the supported list.

Scope: Global Vs Project

By default, skills are installed globally into the agent's home-directory path. Add scope: project to your config, or pass --project on the command line, to install into the current project directory instead.

The --project / --global flags always override whatever scope is set in the config file.

Environment Variables

These environment variables affect Kasetto's output behavior:

Variable	Effect
`NO_TUI`	Disables interactive screens (home menu, list browser). Set to any value.
`NO_COLOR`	Disables colored output. Set to any value.