Aliyun Ccc Manage

Use when managing Alibaba Cloud Cloud Call Center (CCC) via OpenAPI/SDK, including the user is working on CCC operations such as instance/resource management...

Security Scan

The skill's stated purpose (managing Alibaba Cloud CCC) matches the code and instructions, but the SKILL.md expects Alibaba Cloud credentials and use of shared config while the registry metadata declares no required environment variables or primary credential — an inconsistency that should be resolved before trusting the skill.

Purpose & Capability

The skill is genuinely about Alibaba Cloud CCC management and includes a small metadata-fetching script and instructions to use the Alibaba Cloud OpenAPI/SDK — these are coherent with the name/description. However, the registry metadata declares no required environment variables or primary credential even though the runtime instructions explicitly require ALICLOUD_ACCESS_KEY_ID / ALICLOUD_ACCESS_KEY_SECRET (and optionally ALICLOUD_REGION_ID) or a shared credentials file. The missing declaration is an incoherence.

Instruction Scope

SKILL.md confines runtime actions to discovering API metadata, calling CCC APIs via SDK/OpenAPI Explorer, and writing artifacts under output/aliyun-ccc-manage/. The included script only fetches public API metadata from api.aliyun.com and writes JSON/MD to the output directory. This is within the stated scope. Note: SKILL.md instructs to include 'key parameters' in evidence files — be cautious that outputs might accidentally include sensitive identifiers or other context you don't want persisted.

Install Mechanism

No install spec; this is an instruction-only skill with a small Python script. No external downloads or package installs are requested, which is low-risk.

Credentials

The SKILL.md requires Alibaba Cloud credentials (env vars ALICLOUD_ACCESS_KEY_ID, ALICLOUD_ACCESS_KEY_SECRET, optional ALICLOUD_REGION_ID) or a shared config file, but the skill metadata lists no required env vars and no primary credential. That mismatch is a problem: a consumer of the skill would not be alerted by the registry metadata that secrets are needed. Requiring cloud credentials is proportionate to the purpose, but the credential requirements must be declared explicitly and limited to least-privilege.

Persistence & Privilege

The skill is not force-installed (always:false) and does not request persistent system-wide privileges. It writes only to its own output directory and does not modify other skills or system configs.

What to consider before installing

This skill appears to do what it says (discover CCC OpenAPI metadata and help operate CCC via Alibaba Cloud APIs), but the published metadata failed to declare that it needs Alibaba Cloud credentials. Before installing or running it: 1) only use least-privilege ALICLOUD credentials and prefer a dedicated read-only account for discovery; 2) confirm the skill metadata is updated to declare required env vars (ALICLOUD_ACCESS_KEY_ID, ALICLOUD_ACCESS_KEY_SECRET, optional ALICLOUD_REGION_ID) and a primary credential; 3) review the output/aliyun-ccc-manage/ folder after runs to ensure no secrets were written; 4) if you have doubts about the source (homepage unknown, owner ID unfamiliar), ask the publisher for provenance or a signed release. The mismatch between declared requirements and runtime instructions is why this is marked 'suspicious' rather than 'benign.'

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 <ProductCode> --version <Version>

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/aliyun-ccc-manage/

Validation

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

Pass criteria: command exits 0 and output/aliyun-ccc-manage/validate.txt is generated.

Output And Evidence

• Save artifacts, command outputs, and API response summaries under output/aliyun-ccc-manage/.
• 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