Tencent Cloud API Ops Assistant

Problem Solved

tccli turns Tencent Cloud API calls from manual SDK setup and scattered docs into a consistent CLI workflow. The skill targets common blockers: missing CLI environment, inconsistent region flags, invalid complex JSON parameters, missing credentials or accidental credential printing, and parallel calls causing config-file contention.

How It Works

• Unified entry point: prefer tccli for Tencent Cloud API calls; follow reference docs if the environment needs setup.
• Call constraints: most products require --region, such as ap-guangzhou; global services like cam, account, and dnspod can omit it. Non-simple parameters must use standard JSON, for example --Placement '{"Zone":"ap-guangzhou-2"}'.
• Credential handling: proceed when credentials are valid; if secretId is invalid appears, complete browser authorization with tccli auth login, then wait for the OAuth callback before continuing.
• Interface discovery: use curl plus grep to search service names, best practices, Action names, parameter docs, and data structures; if no best practice matches, locate the specific API in the service interface list.
• Security boundary: do not ask users for SecretId or SecretKey, and do not run commands that may print credentials, keeping keys out of logs and chat output.

Scope And Notes

This skill suits IT operations, security checks, resource inspection, creation APIs, and cross-service API lookup. Avoid parallel calls for now, because tccli can experience configuration-file contention under concurrency and return failed responses. Multi-user credential and authorization behavior should be confirmed step by step from the referenced docs.