Skip to main content
Version: 2.0

Use with Agent

Smart Studio publishes the current public-console documentation as static, machine-readable resources. An agent can read these resources to explain a workflow, create a checklist, or help diagnose a documented problem. The agent does not receive access to your Smart Studio account.

FOR HUMANKeep control of the workflowRead the current guide, verify prerequisites, and perform each Console action yourself.

One Instruction

Copy this instruction into a coding or general-purpose agent:

Read https://smartstudio.console.alibabacloud.com/guides/skills.txt and install the Smart Studio Docs 2.0 skill. Ask what I want to accomplish, then use only current public-console documentation to explain the workflow. Do not use archived or compatibility-hidden documentation, and do not operate my account.

The manifest directs the agent to the Skill and the latest Docs 2.0 index on the same site.

Published Resources

ResourceURLPurpose
Skill manifest/guides/skills.txtInstallation and version entry point.
Skill/guides/skills/smart-studio/SKILL.txtRouting, grounding, and safety rules.
Docs index/guides/llms.txtCompact list of current Agent-visible pages.
Full text/guides/llms-full.txtCurrent Agent-visible documentation in one file.
Page text/guides/llms/pages/**.txtOne Markdown-formatted text mirror per current page.

All unversioned Agent resources represent Docs 2.0. They intentionally exclude archived versions, compatibility-hidden capabilities, internal writing guides, and unreleased workflows.

What the Agent Can Help With

  • Prepare an Activate Cluster checklist for your infrastructure.
  • Explain a failed machine-verification or activation state.
  • Guide you through GPU Dashboard.
  • Help choose between Model Gallery and My Models.
  • Prepare deployment, usage, or billing investigation steps.
  • Cite the exact Docs 2.0 pages used in its answer.

Safety Boundary

The Smart Studio Skill must not:

  • Sign in to the Console or perform actions on your behalf.
  • Request or expose passwords, activation tokens, or account credentials.
  • Invent Console fields, commands, or product capabilities.
  • Use an archived page when a current 2.0 page exists.

If the documentation does not answer the question, the Agent must explain what is missing instead of guessing.

Content Freshness

Docs authors continue editing the Markdown/MDX files used by the Human site. Every build regenerates the search index, page mirrors, LLM feeds, and offline Skill bundle. As a result, the Human and Agent entry points consume the same current content.