Tencent Cloud Management Tool
ReviewAudited by ClawScan on May 10, 2026.
Overview
This is a powerful Tencent Cloud administration skill, but it needs review because it handles cloud login tokens and references unreviewed automation scripts that can create paid resources or change DNS.
Install only if you intend to let the agent manage Tencent Cloud resources. Prefer least-privilege Tencent Cloud accounts, treat OAuth codes and `~/.tccli/*.credential` files as sensitive, confirm every paid or destructive operation, and avoid running referenced helper scripts that are not included and reviewed.
Findings (5)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Following this workflow could lead the agent or user to run unreviewed local/external code that creates paid cloud resources, purchases domains, or changes DNS records.
The supplied manifest only includes `scripts/tccli-oauth-helper.py`, not `create_site.py`, `tc.sh`, or the referenced `tencent-cloud-tools` helpers. The referenced missing script would perform high-impact cloud mutations and billing-related actions.
TC="<tencent-cloud-tools>/scripts" python3 $TC/create_site.py ... 脚本自动完成： 1. 创建 Lighthouse 实例 3. 购买域名 5. 添加 DNS A 解析
Remove references to missing helpers, include their reviewed source in the skill, or replace them with explicit tccli commands and require user confirmation before paid or account-changing actions.
A wrong or stale OAuth code could be accepted and stored, causing the agent to operate under an unintended Tencent Cloud account or session.
OAuth state mismatch is an identity-boundary protection. The helper only warns and continues, then can exchange and save credentials from a stale or unexpected authorization response.
if saved_state and token_state != saved_state:
print(f"⚠️ 警告: state 不匹配")
...
print("可能是使用了旧的授权链接。继续尝试...")Fail closed on any state mismatch, clear the saved state, and require the user to generate a fresh authorization URL and code.
Users may underestimate the sensitivity of the local `.tccli` credential file or the authorization code they send to the agent.
The documentation frames OAuth leakage as very limited because temporary credentials expire in 2 hours, but also says credentials are stored locally and automatically refreshed. The helper code stores OAuth refresh-token material, so the risk of the local credential file is understated.
OAuth 方式使用的是临时凭证（2 小时后自动过期失效），即使凭证泄露影响也极为有限。 ... 授权成功后凭证会保存在 `~/.tccli/default.credential` ... tccli 会自动刷新 OAuth 凭证
Clearly explain that the local credential file and OAuth code are sensitive, may enable refreshed access, and should be protected or cleared with `tccli auth logout` when no longer needed.
A mistaken instance ID, disk ID, or device name could create costs or erase data on a cloud server.
The skill documents paid resource creation, disk attachment, and root remote commands that can format disks. This is expected for cloud disk management, but it is high-impact.
tccli cbs CreateDisks ...
tccli cbs AttachDisks ...
tccli tat RunCommand ... --Username "root" ...
parted -s ${DISK} mklabel gpt ... mkfs.ext4 ${DISK}1Before running mutation commands, confirm the target account, region, resource IDs, costs, backups, and whether the disk is truly new.
The target server’s software environment can be changed or broken if the command is run on the wrong host or without understanding the installer.
The deployment guide includes remote software installation and a destructive replacement of `/usr/local/go`. This is common in server deployment workflows, but it executes downloaded installer code and changes the remote host.
curl -fsSL https://get.docker.com | sh ... rm -rf /usr/local/go && tar -C /usr/local -xzf /tmp/go.tar.gz
Review installers before execution, prefer pinned package sources where possible, and confirm before deleting or replacing existing runtime installations.