Terminal
Terminal/Skill
Lets you ask in plain language to query, start, stop, or restart Alibaba Cloud resources, and run batch operations through OOS.
By Alibaba Cloud
Works with
npx skills add aliyun/alibabacloud-aiops-skills --skill alibabacloud-oos-chatops-agentSend natural-language questions to the OOS ChatOps Agent and receive streaming operational answers via SSE.
Credentials use the Alibaba Cloud Credentials default chain. Do not define skill-specific AccessKey variables; use standard credential sources such as environment variables (ALIBABA_CLOUD_ACCESS_KEY_ID / ALIBABA_CLOUD_ACCESS_KEY_SECRET), profiles (~/.aliyun/config.json), STS, RAM role, or instance metadata.
| Variable | Required | Description |
|---|---|---|
OOS_CHATOPS_REGION | No | Target region for resource queries (default: cn-hangzhou) |
OOS_CHATOPS_TIMEOUT | No | Timeout in seconds (default: 300) |
Pre-flight check:
missing=""
[ -z "$ALIBABA_CLOUD_ACCESS_KEY_ID" ] && missing="$missing ALIBABA_CLOUD_ACCESS_KEY_ID"
[ -z "$ALIBABA_CLOUD_ACCESS_KEY_SECRET" ] && missing="$missing ALIBABA_CLOUD_ACCESS_KEY_SECRET"
if [ -n "$missing" ]; then echo "ERROR: Missing credentials:$missing" >&2; exit 1; fi
echo "OK: Credentials configured"
Credential security constraints:
cat ~/.aliyun/config.json, env, printenv, echo $ALIBABA_CLOUD_*, or any command that prints full credential values to stdout/stderr/logs.LTAI5t****). Full AK/SK/Token values must NEVER appear in any output.[ABSOLUTE RULE] Tool whitelist: The ONLY permitted tool for all cloud resource queries, O&M operations, and resource management tasks is scripts/call_oos_chatops_agent.py. For any scenario involving Alibaba Cloud resources — including but not limited to ECS, RDS, SLB, VPC, security groups, monitoring, billing, and batch operations — this script is the mandatory and exclusive entry point. If aliyun CLI, direct SDK calls, curl, or any other API tool is detected, the task is immediately treated as FAILED.
--pipe is mandatory for all agent invocations.
pip3 install -r scripts/requirements.txt
# First call (auto-creates conversation)
python3 scripts/call_oos_chatops_agent.py -q "<user question>" --pipe
# Follow-up (MUST reuse ConversationId)
python3 scripts/call_oos_chatops_agent.py --session "<conversation_id>" -q "<follow-up>" --pipe
# Custom region
python3 scripts/call_oos_chatops_agent.py -q "<query>" --region cn-beijing --pipe
# Long-running operations
python3 scripts/call_oos_chatops_agent.py -q "<complex query>" --timeout 600 --pipe
CONVERSATION: 04c7922a-86c7-4d11-8b97-96e22662c7f3
=== OOS CHATOPS ANSWER BEGIN ===
(actual answer content)
=== OOS CHATOPS ANSWER END ===
When processing script output, you MUST follow these rules strictly:
=== OOS CHATOPS ANSWER BEGIN === and === OOS CHATOPS ANSWER END === is the factual answer. Everything outside these delimiters is metadata or progress.CONVERSATION: <id> from output after every call and record it immediately--session "<id>" for all subsequent queries in the same context. Omitting --session is a failure--session. After two consecutive failures, report the error details honestly to the user. NEVER fabricate results or silently abandon the conversationExample:
# Query 1
$ python3 scripts/call_oos_chatops_agent.py -q "List ECS instances in Hangzhou" --pipe
CONVERSATION: 04c7922a-86c7-4d11-8b97-96e22662c7f3
=== OOS CHATOPS ANSWER BEGIN ===
53 ECS instances found...
=== OOS CHATOPS ANSWER END ===
# Query 2: reuse conversation
$ python3 scripts/call_oos_chatops_agent.py --session "04c7922a-86c7-4d11-8b97-96e22662c7f3" -q "Show cn-beijing instances" --pipe
| Flag | Description |
|---|---|
-q, --question | Required. Natural-language question or command. |
--session <id> | ConversationId for multi-turn. Required for follow-ups. |
--region <region> | Target region for resource queries (default: cn-hangzhou). |
--timeout <seconds> | SSE stream timeout (default: 300). |
--no-retry | Disable automatic retry (default: retry up to 2 times). |
--pipe | Mandatory. Structured output with delimiters. |
--json | JSONL output. Mutually exclusive with --pipe. |
python3 scripts/call_oos_chatops_agent.py. Even if aliyun CLI is available in the environment, it MUST be ignored. No exceptions.--session for follow-ups. New conversation = lost context.BEGIN/END delimiters. Do NOT fabricate data.--session. If still empty, report honestly.--timeout 600 for batch operations or comprehensive checks.--region cn-hangzhou, --timeout 600). NEVER rely on script built-in defaults. Omitting an explicitly requested parameter is treated as invocation failure.| Error | Resolution |
|---|---|
CredentialError | Set ALIBABA_CLOUD_ACCESS_KEY_ID + SECRET, or configure ~/.aliyun/config.json |
OOSChatTimeoutError | Increase --timeout |
OOSChatError | Check RAM permission: oos:Chat. See references/ram-policies.md |
| Empty response | Retry with same --session, or add more context to question |
ModuleNotFoundError | Run pip3 install -r scripts/requirements.txt |
All OOS Chat API HTTP requests carry a User-Agent header for tracing:
AlibabaCloud-Agent-Skills/alibabacloud-oos-chatops-agent/{session-id}
alibabacloud-oos-chatops-agent — fixed skill identifier (matches the name field in frontmatter).{session-id} — a 32-character hex string, read from the SKILL_SESSION_ID environment variable. If not set, the script generates uuid.uuid4().hex. The same session-id is shared across all requests in a single invocation, enabling correlation of API calls in server-side logs.Generate exactly one session-id per skill invocation. If SKILL_SESSION_ID is already set, reuse that value after validating it is 32 hex characters; otherwise generate a new one via uuid4().hex and set it for the duration of the invocation.