Tencent

Route ambiguous Tencent requests to product families and generate region-safe decision records.

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/dingdyan/openclaw-workspace-v2 --skill tencent
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Tencent
Source: https://github.com/dingdyan/openclaw-workspace-v2/tree/main/skills/tencent
Command: npx skills add https://github.com/dingdyan/openclaw-workspace-v2 --skill tencent

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It helps you resolve ambiguity across Tencent’s many surfaces by producing safer, region-aware guidance and using official sources to validate time-sensitive product or compliance details.

Core Features & Use Cases

  • Tencent surface routing: Classifies the request into Tencent corporate strategy, Tencent Cloud, WeChat ecosystem, WeCom, payments/commerce, ads/growth, or games/content so the answer targets the right owner and workflow.
  • Region and audience clarity: Enforces explicit mainland China vs Hong Kong/Singapore/global assumptions and calls out how availability, compliance, and onboarding differ.
  • Official-source verification: Prioritizes Tencent-owned documentation and records translation mismatches, preventing “translated summary” errors from becoming false facts.
  • Decision record + lightweight memory: Produces a concise decision record and stores only durable, non-secret context under ~/tencent/ to keep later Tencent work consistent.

Quick Start

Ask: “I need a Tencent Cloud architecture for a workload launched to mainland users—what regions, products, and rollout checks should I consider, and what official sources must we verify first?”

Frequently Asked Questions about Tencent

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I plan a Tencent Cloud architecture for mainland users?

To plan Tencent Cloud architecture for mainland users, you must define explicit geography and audience assumptions first. The framework routes requests to Tencent Cloud, enforcing region-safe recommendations and verifying official documentation before rollout.

How do I verify official Tencent product details when ownership is unclear?

Verifying official Tencent product details requires prioritizing Tencent-owned documentation and recording translation mismatches. This prevents translated summary errors from becoming false facts when corporate naming or product ownership is ambiguous.

What's the best way to route ambiguous WeChat ecosystem decisions?

The best way to route ambiguous WeChat ecosystem decisions is to classify the request into WeChat, WeCom, payments, or ads workflows. This ensures the answer targets the correct product family and applies region-aware compliance checks.

Does Tencent Cloud architecture planning separate execution rights from planning?

Yes, Tencent Cloud architecture planning explicitly separates planning from execution rights. The framework produces an end-state decision record using local memory under ~/tencent/ to maintain consistency without granting execution privileges.

Can I use this framework for Hong Kong versus global Tencent Cloud rollout checks?

Yes, you can use this framework for Hong Kong versus global Tencent Cloud rollout checks. It enforces explicit mainland China versus Hong Kong or global assumptions, calling out how availability, compliance, and onboarding differ across regions.

Why do translated Tencent documentation summaries cause false facts?

Translated Tencent documentation summaries cause false facts when translation mismatches go unrecorded. The framework prioritizes official sources and reconciles translation discrepancies to prevent errors in time-sensitive product or compliance details.