SKO Workshop

This repo is the hands-on workspace for the SKO workshop. It contains the declarative SAM configuration and step-by-step guides you will follow during the session.

Table of Contents

• Environment Setup
  • Prerequisites
  • If using Docker solace broker: Add the Solace Broker to the Docker Network
• Getting Started

Environment Setup

Prerequisites

All required executables will be shared the day of the workshop. There are executables for Client, CLI, and Docker; choose the appropriate endpoint.

1. SAM Client (in the client folder, install the OS target)

   1. SAM Desktop executable: SolaceAgentMesh.dmg or sam-desktop-enterprise.exe

      Note: On MacOS, after dragging the app to your Applications execute the following:

      xattr -cr /Applications/Solace\ Agent\ Mesh.app

      Note: On Windows, if your .exe does not load run the following from Powershell

      Start-Process .\sam-desktop-enterprise.exe
      # if you get any errors with Start-Process
      .\sam-desktop-enterprise.exe

      

      Follow the steps to configure SAM Desktop:

      • Get Started
      • Configure a model now
      • Enter LiteLLM key manually
      • From "Service" Choose Custom as service type
      • Put https://lite-llm.mymaas.net/ as endpoint then click "Looks good"
      • Choose claude-sonnet-4-6 as the model
      • Test connection and make sure you get a success
      • Choose built-in

      

   2. OR The sam-enterprise Docker image loaded locally

      docker load -i sam-enterprise-latest.tar.gz
      docker compose up
      

      Note: you can use podman instead

2. SAM cli installed in a dedicated dir from one drive

   Note: make sure you do not have any sam command installed on your system To confirm, open a terminal session and just type sam you should see no command found

   cd <path_to_dir_where_cli_downloaded>
   # Make sure the executable is called sam
   # Note: Replace the executable name to match what you installed
   mv sam-enterprise sam
   # MacOS / Linux / WSL
   chmod +ux sam
   xattr -cr sam
   
   # Make sure to add the sam cli to your path and update your .profile (e.g. ~/.zshrc)
   echo "export PATH=$PATH:$PWD" >> ~/.zshrc 
   source ~/.zshrc 
   # Confirm sam is working
   sam -h

   On Windows

   • System Properties > Environment Variables > in System Variables edit the Path variable. Add New variable and include the dir where sam.exe is.
   • Note: you can test it in a new terminal session

3. A LiteLLM API token

4. VsCode (or any code editor with an ai-assisted tool)

5. Claude Code installed (claude --version) and configured

6. [Optional] Solace Broker

   1. Docker with a running Solace broker container attached to the sam-network bridge network
   2. OR you can use Solace Cloud instead

If using Docker solace broker: Add the Solace Broker to the Docker Network

If not already, get the solace broker running locally

The SAM container must reach the Solace broker by container name (solace). Both must be on the same Docker bridge network:

# Create the shared network if it does not exist
docker network create sam-network

# If your Solace broker container is already running, connect it
docker network connect sam-network solace

Getting Started

Follow the guides in the guides directory, starting with

1. Getting Started
2. Hiring
3. Onboarding
4. Coaching
5. Supervision
6. Teamwork
7. Improvement