Skip to main content
Use the workspace’s Agent Skills to turn a task, dataset, or existing agent into a runnable Osmosis rollout. For a known-good example with no design work, start with the Multiply Quickstart.
This guide assumes you have completed Onboarding: your workspace repository is cloned, the CLI is installed and authenticated, and your AI coding environment is open in the workspace directory.

How Workspace Skills Work

Platform-created workspace repositories include project-local Agent Skills under .agents/skills/. An agent that loads these skills can select the workflow for the current stage:
The skills call the Osmosis CLI for workspace checks, dataset validation, evaluation runs, and training preflight. They do not replace the CLI.

When to Use This Path

Use the Skills in Your Workspace Repository

Open your platform-created workspace repository in your AI coding environment. The repository includes the workspace contract and Agent Skills alongside rollout code, configs, and data:
AGENTS.md contains the always-loaded workspace contract. .agents/skills/ contains the canonical workflow skills, and .claude/skills/<skill-name> exposes the same skills to Claude Code through symlinks back to .agents/skills/.

Verify the Workspace

Before asking the agent to write rollout code, confirm that the CLI can resolve the workspace:

Ask the Agent to Plan from the Dataset

Describe the task and ask the agent to begin with the workspace’s planning skill:
The workspace skills guide the agent through these stages:
1

Plan training

Inspect data/, existing rollouts, and workspace config, then settle the dataset schema before writing rollout code.
2

Create or adapt a rollout

Write the smallest AgentWorkflow and Grader that can load, run, and score samples. Generated files should stay under rollouts/, configs/eval/, configs/training/, and data/.
3

Submit an evaluation run

Push the rollout to the workspace repository and submit an evaluation run as the quality gate:
4

Debug until the evaluation run is clean

Fix loading, dataset, grader, dependency, and reward issues before training. A healthy evaluation run is the handoff from creation to training readiness.
5

Prepare a training run

Once the rollout is validated, let the agent inspect the training run config and run submit-time preflight. Submit only when you are ready to start a platform training run.
Do not skip the evaluation run gate. osmosis train submit should be the step after the rollout cleanly loads, runs, and grades samples on the platform.

Workspace Skills

The workspace skills are organized around rollout creation stages: You usually do not need to invoke a skill by name. Describe the outcome; an agent that loads the repository’s Agent Skills selects the matching workflow.

Next Steps

SDK Overview

Understand the AgentWorkflow and Grader contract behind generated rollout code.

Evaluation

Validate rollouts with an evaluation run before submitting a training run.

Git Sync

Push rollout changes and let the platform sync the code version used for evaluation runs and training runs.

Training Runs

Submit and monitor a training run after the evaluation run passes.
Last modified on August 10, 2026