# Smart Studio Skills

Documentation version: **2.0**

Use this manifest to install the Smart Studio documentation Skill from the
same origin as the current public Console documentation.

## Install with Your Agent

1. Read [`./skills/smart-studio/SKILL.txt`](./skills/smart-studio/SKILL.txt).
2. Install the `smart-studio-integration` Skill in the agent's supported local
   Skill directory.
3. Keep every documentation request on the same origin as this file.
4. Read `/guides/llms.txt` to discover current Docs 2.0 pages.
5. Read the current release notes at
   [`/guides/llms/pages/changelog/2.0.0.txt`](/guides/llms/pages/changelog/2.0.0.txt)
   when the request concerns availability, migration, or recent changes.
6. Ask the user what they want to accomplish before selecting a workflow.

## Supported Docs 2.0 Workflows

| User goal | Start with |
| --- | --- |
| Prepare GPU infrastructure | BYO-GPU Quickstart |
| Connect and validate machines | Activate Cluster |
| Inspect cluster or serving health | GPU Dashboard |
| Select a platform model | Model Gallery |
| Upload or manage a custom model | My Models |
| Create or operate a model service | Deployments |
| Prepare, train, or evaluate a model | Datasets, Fine-Tuning, Evaluations |
| Investigate resource consumption | Usage |
| Investigate charges | Billing |

## Version and Visibility Rules

- Treat the unversioned `/guides/llms*` resources as Smart Studio Docs 2.0.
- Do not read or cite archived, version-prefixed documentation.
- Do not use compatibility-hidden API Reference, Router, Secrets, Provider
  Keys, or Gateway pages for current public-cloud guidance.
- If a capability is absent from the current index, say that it is not
  documented as available instead of borrowing instructions from another
  Smart Studio environment.

## Safety Rules

- Explain workflows and generate documented configuration examples only.
- Do not sign in, click Console actions, change resources, or operate the
  user's account.
- Never request, expose, persist, or print credentials, passwords, or
  activation tokens.
- Do not invent fields, commands, statuses, or product capabilities.
- Cite the Docs 2.0 pages used in the answer.