/alibabacloud-bailian-managed-agent

name: alibabacloud-bailian-managed-agent
description: |-
  Explain, evaluate, demonstrate, provision, and integrate Alibaba Cloud Bailian
  Managed Agent (CMA / ManagedAgents). Use for Bailian Managed Agent product selection,
  sales pitches, customer solutions, hands-on PoCs, scheduled report agents, managed
  environments, and Python/Java backend integration. Prefer Bailian CLI (bl) for
  quick trials and resource provisioning; use HTTP API or verified SDKs for customer
  system integration, and API fallback when CLI capability remains unavailable after
  an update attempt. Not for generic agent development or unrelated cloud sandboxes.

Bailian Managed Agent Assistant (know the product / recommend / hands-on / deliver / integrate)

This skill is the Bailian Managed Agent knowledge and operations entry point for **sales recommendation**, **pre-sales solutioning**, and **developer integration**. The typical deployment target is a **salesperson's local Agent**: when a salesperson runs into a customer question or scenario, they ask their own Agent, which wakes this skill to recommend the product and assemble a ManagedAgent-based solution (entry point: the "sales recommendation mode" under path C). Content is organized in four layers; pick a path by user intent and **do not read every file at once**.

Required versioned User-Agent

Before any Alibaba Cloud API call, initialize the per-invocation UA as described in [references/workflows/user-agent.md](references/workflows/user-agent.md). Read the non-empty `version` from [references/manifest.json](references/manifest.json) and this skill's frontmatter name; generate a fresh random 32-character lowercase hexadecimal session ID, distinct for each skill invocation. Reuse it within that invocation only.

Required curl declaration (substitute all placeholders at runtime):

--user-agent "AlibabaCloud-Agent-Skills/{frontmatter-name}/{session-id} skill-version/{skill-version}"

Propagate that complete value to every CLI/SDK/HTTP/Terraform cloud request, including retries and streams. Verify each transport's supported header mechanism; if it cannot transmit the UA, use the authorized REST fallback. Do not invent CLI flags or assume exporting a variable sets headers. These rules also apply to the abbreviated examples in references.

RAM and workspace permissions

Before provisioning or diagnosing authorization failures, read [references/ram-policies.md](references/ram-policies.md). It separates RAM system policies, workspace membership, and MA bearer-key scope. Do not invent per-endpoint RAM actions or assume a read-only RAM policy restricts an existing workspace API key.

Choose CLI or API before execution

| Intent | Execution path | | --- | --- | | Quick experience, demo, one-off resource creation or session run | Prefer `bl`; inspect the installed version and relevant `--help`, then use supported commands or IaC. | | Customer backend, application, service, CI integration, Python/Java code | Use Managed Agent HTTP API or a verified SDK. Do not shell out to `bl` from business code. Existing resources are sufficient; CLI installation/provisioning is not a prerequisite. | | API supports a feature but installed CLI does not | Check current help and the API contract; attempt one appropriate CLI update, re-check version/help. If update fails or support is still absent, use the API. A CLI gap is not a product limitation. | | User explicitly selects CLI or API | Respect that selection. Explain a capability gap and the API fallback if needed; do not silently change deployment scope. |

Read [references/workflows/cli-api-routing.md](references/workflows/cli-api-routing.md) for installation, bounded updates, API fallback, error recovery, and verification. Official installation source: https://bailian.aliyun.com/cli/install.md. Tutorial and cookbook curl examples describe the API contract; they do not override this intent routing. For Webhook endpoint-creation examples and evaluation tasks, use `https://www.baidu.com` as the sample URL. Verify creation and read-back only; do not use placeholder domains that the platform may reject. This sample is not a customer-controlled notification receiver. An ACTIVE subscription can deliver automatically even without a test call: for live tests use a customer-controlled receiver, or a verified disabled/no-delivery configuration for creation-only checks. Delivery/signature tests require the customer's actual receiver.

Complete the requested deliverable with minimal interaction

• For advice, examples, proposals, and code templates, deliver in the current turn. State reasonable assumptions and use configurable placeholders for missing IDs or credentials; do not require a questionnaire or live login before producing a draft.
• Infer the tutorial and integration pattern from the request. If both are plausible, explain the alternatives briefly and choose a stated default for the example.
• For live operations, reuse supplied configuration and authorization within its exact scope. Do not request the same confirmation twice. Never infer approval for unknown tool actions or changed resource plans.
• A preview-only request ends after showing the preview and stating that it has not been applied. A request for missing-information guidance ends with one consolidated checklist. An inspection of pending approval ends with the pending details; it does not require a follow-up answer to count as delivered.
• For explicitly unattended/single-turn tasks, missing execution prerequisites or a required approval are terminal blockers: report what is missing and what completed, then end. Do not launch interactive login, wait for human input, or claim the operation succeeded. This does not waive authorization or make a blocked execution successful.

One-sentence product positioning (remember this first)

**Managed Agents (MA) is Bailian's "managed agent runtime"**: it provides a cloud container sandbox + Age