← Back to Skills Marketplace
cinience

Alicloud Ai Cloud Call Center

by cinience · GitHub ↗ · v1.0.3 · MIT-0
cross-platform ⚠ suspicious
1143
Downloads
0
Stars
2
Active Installs
4
Versions
Install in OpenClaw
/install alicloud-ai-cloud-call-center
Description
Manage Alibaba Cloud Cloud Call Center (CCC) via OpenAPI/SDK. Use whenever the user is working on CCC operations such as instance/resource management, config...
README (SKILL.md)

Category: service

Cloud Call Center

Use Alibaba Cloud OpenAPI (RPC) with official SDKs or OpenAPI Explorer to manage resources for Cloud Call Center.

Workflow

  1. Confirm region, resource identifiers, and desired action.
  2. Discover API list and required parameters (see references).
  3. Call API with SDK or OpenAPI Explorer.
  4. Verify results with describe/list APIs.

AccessKey priority (must follow)

  1. Environment variables: ALICLOUD_ACCESS_KEY_ID / ALICLOUD_ACCESS_KEY_SECRET / ALICLOUD_REGION_ID Region policy: ALICLOUD_REGION_ID is an optional default. If unset, decide the most reasonable region for the task; if unclear, ask the user.
  2. Shared config file: ~/.alibabacloud/credentials

API discovery

  • Product code: CCC
  • Default API version: 2020-07-01
  • Use OpenAPI metadata endpoints to list APIs and get schemas (see references).

High-frequency operation patterns

  1. Inventory/list: prefer List* / Describe* APIs to get current resources.
  2. Change/configure: prefer Create* / Update* / Modify* / Set* APIs for mutations.
  3. Status/troubleshoot: prefer Get* / Query* / Describe*Status APIs for diagnosis.

Minimal executable quickstart

Use metadata-first discovery before calling business APIs:

python scripts/list_openapi_meta_apis.py

Optional overrides:

python scripts/list_openapi_meta_apis.py --product-code \x3CProductCode> --version \x3CVersion>

The script writes API inventory artifacts under the skill output directory.

Output policy

If you need to save responses or generated artifacts, write them under: output/alicloud-ai-cloud-call-center/

Validation

mkdir -p output/alicloud-ai-cloud-call-center
for f in skills/ai/service/alicloud-ai-cloud-call-center/scripts/*.py; do
  python3 -m py_compile "$f"
done
echo "py_compile_ok" > output/alicloud-ai-cloud-call-center/validate.txt

Pass criteria: command exits 0 and output/alicloud-ai-cloud-call-center/validate.txt is generated.

Output And Evidence

  • Save artifacts, command outputs, and API response summaries under output/alicloud-ai-cloud-call-center/.
  • Include key parameters (region/resource id/time range) in evidence files for reproducibility.

Prerequisites

  • Configure least-privilege Alibaba Cloud credentials before execution.
  • Prefer environment variables: ALICLOUD_ACCESS_KEY_ID, ALICLOUD_ACCESS_KEY_SECRET, optional ALICLOUD_REGION_ID.
  • If region is unclear, ask the user before running mutating operations.

References

  • Sources: references/sources.md
Usage Guidance
This skill appears to be functionally aligned with managing Alibaba Cloud CCC, but it has a practical mismatch: the documentation requires your Alibaba access key and/or shared credentials file while the registry metadata does not declare those requirements. Before installing or running it: 1) Verify the skill's source and trust the publisher (no homepage provided). 2) Only provide least-privilege Alibaba credentials and prefer a throwaway or scoped key for testing. 3) Confirm the agent will be prompted for ALICLOUD_* env vars or that you supply them in a controlled environment; do NOT paste long-lived credentials into chat. 4) Expect the skill to write API responses and evidence to output/alicloud-ai-cloud-call-center/ — review those files for sensitive data and remove them when done. 5) If you need stronger assurance, ask the publisher to update registry metadata to declare required env vars and config paths, and to document exactly what will be written to disk.
Capability Analysis
Type: OpenClaw Skill Name: alicloud-ai-cloud-call-center Version: 1.0.3 The skill bundle is a legitimate tool for managing Alibaba Cloud Cloud Call Center (CCC) resources. The primary script, `scripts/list_openapi_meta_apis.py`, fetches public API metadata from official Alibaba Cloud endpoints (api.aliyun.com) to assist the agent in discovering service capabilities. The instructions in `SKILL.md` follow standard security practices, such as recommending least-privilege credentials and using environment variables for authentication.
Capability Assessment
Purpose & Capability
The skill claims to manage Alibaba Cloud CCC and its SKILL.md explicitly requires ALICLOUD_ACCESS_KEY_ID / ALICLOUD_ACCESS_KEY_SECRET (or ~/.alibabacloud/credentials) and a region; however the registry metadata lists no required environment variables, no primary credential, and no config paths. That inconsistency is disproportionate to the declared metadata and may mislead users about what secrets the skill needs.
Instruction Scope
Runtime instructions are generally within the stated purpose (discover API metadata, call APIs, verify results). They explicitly prioritize env vars and a shared credentials file and instruct writing API responses and evidence under output/alicloud-ai-cloud-call-center/. Asking to save request/response evidence is reasonable for reproducibility but increases risk of persisting sensitive info (resource identifiers, potentially token-like data) to disk. The SKILL.md does not instruct contacting any endpoints outside Alibaba's official meta API (the included script fetches api.aliyun.com).
Install Mechanism
No install spec; the skill is instruction-only with a small helper script that performs only an HTTPS GET to an official Alibaba meta endpoint and writes JSON/MD to the local output directory. No third-party downloads or extracted archives are present.
Credentials
The SKILL.md requires sensitive credentials (ALICLOUD_ACCESS_KEY_ID and ALICLOUD_ACCESS_KEY_SECRET) and optionally reading ~/.alibabacloud/credentials, but these are not declared in the skill's registry 'requires' metadata. That mismatch could prevent appropriate prompts, auditing, or least-privilege enforcement and may cause accidental credential exposure when outputs are written to disk.
Persistence & Privilege
always:false and disable-model-invocation:false (normal). The skill does not request forced always-on presence and does not modify other skills or global agent config. It writes artifacts only under its declared output directory.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install alicloud-ai-cloud-call-center
  3. After installation, invoke the skill by name or use /alicloud-ai-cloud-call-center
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.3
batch publish from alicloud-skills on 2026-03-11
v1.0.2
batch publish from alicloud-skills on 2026-02-13
v1.0.1
Initial ClawHub publish for Alibaba Cloud skills with agents metadata.
v1.0.0
Initial ClawHub publish for Alibaba Cloud skills with agents metadata.
Metadata
Slug alicloud-ai-cloud-call-center
Version 1.0.3
License MIT-0
All-time Installs 2
Active Installs 2
Total Versions 4
Frequently Asked Questions

What is Alicloud Ai Cloud Call Center?

Manage Alibaba Cloud Cloud Call Center (CCC) via OpenAPI/SDK. Use whenever the user is working on CCC operations such as instance/resource management, config... It is an AI Agent Skill for Claude Code / OpenClaw, with 1143 downloads so far.

How do I install Alicloud Ai Cloud Call Center?

Run "/install alicloud-ai-cloud-call-center" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Alicloud Ai Cloud Call Center free?

Yes, Alicloud Ai Cloud Call Center is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Alicloud Ai Cloud Call Center support?

Alicloud Ai Cloud Call Center is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Alicloud Ai Cloud Call Center?

It is built and maintained by cinience (@cinience); the current version is v1.0.3.

💬 Comments