AI Agent Hub
Back to skills
CloudQ Multi-Cloud Ops Assistant icon

CloudQ Multi-Cloud Ops Assistant

IT Ops & Security Updated 2026.08.30

Paste the following prompt into your AI chat to install this skill:

Please install @user_15292d5a/yjkj-cloudq according to https://skillhub.cn/install/skillhub.md.

About this skill

Problem

CloudQ targets the operational friction of cloud workflows where entry points are scattered, tool switching is frequent, and context is easy to lose. It brings multi-cloud resource queries, architecture governance, and advisor Q&A into natural-language conversations, suitable for WorkBuddy, Qclaw, LightClaw, or IM channels such as WeChat, WeCom, Feishu, DingTalk, and Slack.

How It Works

  • Auth first: supports OAuth and AK/SK credentials, with subaccounts recommended for ReadOnlyAccess and QcloudAdvisorAccessForCloudQ.
  • Conversation loop: after starting an SSE request, keep chat_id and session_id, then poll until completed, failed, or timeout, avoiding duplicate submissions.
  • Context retention: follow-up questions must reuse the initial session_id; regenerate only for explicit new conversations or platform session resets.
  • Output handling: backend content is rendered as returned, preserving links; architecture diagrams can be generated locally with HTML + Mermaid.
  • Safety scope: calls are limited to the Tencent Cloud advisor interface whitelist and approved service domains.

Boundaries

CloudQ handles cloud, multi-cloud, and ITOM tasks only. Coding, casual chat, translation, and general knowledge requests are rejected. Protocol consent, resource write actions, and cleanup scripts require explicit user confirmation; network and transient server errors allow limited retries.

Use Cases

  • Ask in IM about VPC, ECS, and LB configs in a region to get a Tencent Cloud resource inventory.
  • Review production architecture before release, list resources, and generate a Mermaid diagram.
  • Find idle resources and cost optimization items, then identify instances that can be offlined.
  • Compare Tencent Cloud, AWS, and Azure equivalent services during multi-cloud selection.

Best For

  • SREs who need quick resource inventories, architecture relationships, and anomaly checkpoints.
  • FinOps engineers looking for idle instances, capacity anomalies, and cost optimization items.
  • On-call ops engineers handling IM alerts who need fast cloud status checks and troubleshooting clues.
  • Cloud architects who must assess architecture risks and generate visual diagrams.