Skip to content

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).

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

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

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

kst sync --dry-run

Explicit MCP Pack Path (mcps.path)

If a repo contains multiple MCP config files or doesn't match the default discovery layout, point directly at one:

mcps:
  - source: https://github.com/acme/monorepo
    path: mcps/servers/pack.json