Agent Quickstart
1. State the environment and goal
Tell the Agent which authorized MSP environment to use and choose one goal: Deployment, Dataset, Training, or Evaluation. Do not paste credentials.
2. Load the Skill
Use $msp-operations. Check the installed sstudio version and the current
capability manifest. For my requested workflow, load only the relevant
reference, report what is enabled, and prepare a safe plan. Do not execute a
pending, disabled, or denied capability.
For one-session use, copy this origin-aware instruction instead:
Preparing the current documentation URL…
3. Check version and identity gates
CLI discovery, the local version check, whoami, and all four Read stages are
enabled. Deployment, Dataset Preparation, and Evaluation Preview are enabled;
Training Preview remains verify-before-release. Deployment create, wait, and
verify are enabled after a successful Preview, while Dataset Preparation,
Training, and Evaluation wait and verify remain verify-before-release.
The Agent may use the existing authorized Profile for an enabled stage without
opening its credentials file. It must stop when command -v sstudio cannot
find the CLI, the version differs from the manifest, or the exact requested
stage is not enabled.
4. Review the plan
A useful plan includes:
- Target environment and requested outcome.
- Chosen SDK or CLI surface and version.
- Current identity and permission evidence when enabled.
- Exact resource identifiers and fields still needed.
- Preview result when enabled.
- Resource impact, idempotency basis, bounded wait, and verification route.
- Capability status and the reason for any stopped action.
5. Execute only an enabled capability
Model Deployment Create is enabled. A current request that explicitly asks the Agent to deploy the normalized outcome counts as execution confirmation; ask only when a missing choice materially changes resource use, cost, or the requested result. Dataset, Training, and Evaluation writes plus uploads, updates, stop/restart, cancel, delete, and other lifecycle mutations remain disabled.
See Permissions and Safe Operations and Troubleshooting for failure behavior.