Cookbook

When you need this: You want copy-paste setups for common real workflows (teams, monorepos, multiple agents, pinned rollouts).

What you'll learn:

Patterns that work well in practice
How to pin and roll out changes safely

Team Bootstrap From A URL Config

Host a shared kasetto.yaml somewhere reachable over HTTPS (public or private), then have each developer run:

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

For private configs hosted on git providers, set the matching token env var (see Authentication).

Inheriting From A Team Or Org Base

Use extends to compose configs. A common pattern: an org-wide base, a team overlay, and a per-project file that narrows or pins specific entries.

# project/kasetto.yaml
extends:
  - https://github.com/acme/skills-base/raw/main/kasetto.yaml
  - https://example.com/team/overlay.yaml
 
scope: project
 
skills:
  # Same source as the base → narrows the parent's skills list to one entry.
  - source: https://github.com/anthropics/skills
    skills:
      - skill-creator
 
  # New source → appended on top of the inherited list.
  - source: https://github.com/acme/internal-pack
    skills: "*"

Top-level scalars (scope, agent, destination) replace. skills and mcps merge by (source, ref-or-branch, sub-dir) identity. See Configuration → Extending Another Config for the full merge-rules table.

Monorepo: Project Scope Per Workspace

Keep one kasetto.yaml per workspace folder and make it project-scoped:

scope: project
agent: cursor
 
skills:
  - source: https://github.com/acme/monorepo-skills
    skills:
      - code-reviewer
      - doc-coauthoring

Then run sync from each workspace directory:

kst sync

Each workspace gets its own ./kasetto.lock.

Multiple Agents From One Config

Install the same skills (and MCP servers) into multiple agents:

agent:
  - claude-code
  - cursor
  - codex
 
skills:
  - source: https://github.com/acme/skills
    skills: "*"
 
mcps:
  - source: https://github.com/acme/mcp-packs
    mcps: "*"

MCP Packs: Pinning And Rollouts

Pin an MCP pack source to a git tag or commit SHA:

agent: claude-code
 
skills:
  - source: https://github.com/acme/skills
    skills: "*"
 
mcps:
  - source: https://github.com/acme/mcp-packs
    ref: v2.4.1
    mcps: "*"

Roll forward by bumping ref, then use --dry-run to preview:

kst sync --dry-run

Explicit MCP Entries (`mcps.mcps`)

If a repo contains multiple MCP files or uses a non-standard layout, list entries explicitly. Plain strings look up mcps/<name>.json; objects let you override the directory:

mcps:
  # Names resolved from mcps/ dir (auto .json extension)
  - source: https://github.com/acme/monorepo
    ref: v1.4.0
    mcps:
      - github        # → mcps/github.json
      - linear        # → mcps/linear.json
 
  # Custom directory via { name, path }
  - source: https://github.com/acme/other
    mcps:
      - name: my-server
        path: tools   # → tools/my-server.json