lhanyun

Tencent Cloud Lighthouse

IT運用・セキュリティv1.0.2
作者:lhanyun更新日 2026-05-18全 3 バージョン · 最新版の公開日 2026-05-08tencentcloud-lighthouse-skill
#Deploy

AlphaMoatによると、2026-10時点でTencent Cloud Lighthouseのダウンロード数は13,484、スター数は1で、累計ダウンロード数で今回のランキング対象AIスキル10,914件中2,066位、IT運用・セキュリティでは502件中66位です。

一覧の初期表示は累計ダウンロード数順で、スター数順にも並べ替えできます。詳細ページの順位は累計ダウンロード数で計算しています。

ダウンロード数
1.3万
スター数
1
累計ダウンロード順位
#2,066
全体の上位 19% · IT運用・セキュリティの上位 14%
プラットフォームダウンロード数スター数コメント
ClawHub ↗1.3万1-

プラットフォームごとに集計方法と集計時点が異なります。

このスキルでできること

インスタンス、配備、防火壁、監視、スナップショット、通信量、TATを扱います。有効な認証が必要で、標準はブラウザーOAuthです。実IDと地域を取得し引数を確認します。再起動、防火壁変更、遠隔命令は確認し、削除や復元は重ねて確認します。CVMのAPIとは区別します。

資料公開日 2026-10-27

できること

  • 軽量サーバーの状態確認や運用を計画する

使う場面

  • 対象がTencent Cloud Lighthouseであるとき

プロンプト例

スキルのドキュメントをもとに生成した例であり、実際の実行結果ではありません。

先に実IDと地域を確認し、変更案の影響に応じた確認を得てから実行して。

月次の推移

ダウンロード数1.3万
1.3万1.3万1.4万2026-09 · ダウンロード数 1.3万2026-10 · ダウンロード数 1.3万26-0926-10
スター数1
0122026-09 · スター数 12026-10 · スター数 126-0926-10
月ダウンロード数前月比スター数
2026-101.3万—1
2026-091.3万—1

SKILL.md 原文

作者が公開した元のファイルをテキストのまま表示しています。AlphaMoat による編集や審査はしていません。リンクはクリックできません。コマンドは内容を確認してから実行してください。取得日 2026-10-23。

8.6 KB・ClawHub v1.0.2
---
name: tencentcloud-lighthouse-skill
description: 'Load when: user mentions Lighthouse, 轻量应用服务器, 轻量服务器, or asks to check/create/manage/deploy Lighthouse instances, deploy applications to Lighthouse, manage Lighthouse firewall rules, reset Lighthouse password, view Lighthouse snapshots/images/traffic, monitor Lighthouse metrics, run commands on Lighthouse via TAT, or asks to get/identify the current instance ID. Trigger phrases: "查看轻量服务器", "Lighthouse实例", "轻量应用服务器", "部署应用", "部署程序", "部署到Lighthouse", "管理防火墙规则", "重置密码", "查看快照", "查看流量包", "获取实例ID", "查看实例ID", "当前实例", "实例IP", "check Lighthouse", "create Lighthouse", "deploy app", "deploy application", "Lighthouse firewall", "Lighthouse snapshot", "instance ID", "whoami". NOT for CVM, CBS, VPC, or other non-Lighthouse products.'
metadata:
  {
    "openclaw":
      {
        "emoji": "☁️",
        "requires": {},
        "install":
すべて表示(全 198 行)
          [
            {
              "id": "pip",
              "kind": "pip",
              "package": "tccli",
              "bins": ["tccli"],
              "label": "Install TCCLI",
            },
          ],
        "references":
          [
            "instance-management",
            "application-deployment",
            "monitoring-alerting",
            "firewall-management",
            "remote-command-tat",
            "snapshot-blueprint",
            "traffic-package",
          ],
      },
  }
---

# Lighthouse Cloud Server Operations

Manage Tencent Cloud Lighthouse instances via tccli CLI.

Your knowledge of tccli parameters and API limits may be outdated.
**Always use `tccli <service> <action> --help` to verify parameters before execution.**

## Prerequisites

```bash
tccli --version
```

If not installed: `pip install tccli`

## Credential Setup

| Method | Security | Expiry | Recommendation |
|--------|----------|--------|----------------|
| OAuth browser login | High | Temporary, expires in 2 hours | Recommended |
| AK/SK key pair | Low | Permanent unless revoked | Special cases only |

When the user has not chosen a method, default to OAuth.

### OAuth Login (Recommended)

Use `script/tccli-oauth-helper.sh` for non-interactive OAuth login:

```bash
# Step 1: Check credential status
bash script/tccli-oauth-helper.sh --status

# Step 2: Generate authorization URL (if credentials are missing or expired)
bash script/tccli-oauth-helper.sh --get-url

# Step 3: User opens the URL in browser, completes login, and gets a base64 code

# Step 4: Complete login with the code
bash script/tccli-oauth-helper.sh --code "base64_code_from_browser"

# Step 5: Verify
tccli lighthouse DescribeRegions
```

**Workflow:**
1. Run `--status` to check existing credentials
2. If expired/missing, run `--get-url` — show the URL to user
3. User opens URL → logs in → copies the base64 code from browser
4. Run `--code` with the base64 code to complete login
5. Verify with `tccli lighthouse DescribeRegions`

**Notes:**
- Credentials are temporary (expires in ~2 hours)
- State is valid for 10 minutes after `--get-url`
- Do NOT use `tccli sts GetCallerIdentity` to verify — it does not support OAuth credentials

### AK/SK Setup

Only if the user explicitly provides SecretId and SecretKey:

```bash
tccli configure set secretId <SecretId>
tccli configure set secretKey <SecretKey>
tccli configure set region ap-guangzhou
```

### Logout

```bash
tccli auth logout
```

## Quick Reference

| Task | Command |
|------|---------|
| List instances | `tccli lighthouse DescribeInstances --region <region>` |
| Instance details | `tccli lighthouse DescribeInstances --region <region> --InstanceIds '["lhins-xxx"]'` |
| Firewall rules | `tccli lighthouse DescribeFirewallRules --region <region> --InstanceId lhins-xxx` |
| Monitoring data | `tccli monitor GetMonitorData --Namespace QCE/LIGHT_HOUSE ...` |
| Run remote command | `tccli tat RunCommand --region <region> --InstanceIds '["lhins-xxx"]' --Content "..."` |
| Snapshots | `tccli lighthouse DescribeSnapshots --region <region>` |
| Traffic packages | `tccli lighthouse DescribeInstancesTrafficPackages --region <region> --InstanceIds '["lhins-xxx"]'` |
| Available regions | `tccli lighthouse DescribeRegions` |
| Help for any action | `tccli lighthouse <Action> --help` |
| Get current instance ID | `bash script/whoami.sh` or `bash script/whoami.sh --id` |

## Scenario Routing

Read the corresponding reference file before executing:

```
User wants to...
├─ Query / start / stop / reboot instances  -> references/instance-management.md
├─ Reset password / view blueprints         -> references/instance-management.md
├─ Deploy applications / verify deployment   -> references/application-deployment.md
├─ View CPU / memory / bandwidth metrics    -> references/monitoring-alerting.md
├─ Set up alarm policies                    -> references/monitoring-alerting.md
├─ Manage firewall rules                    -> references/firewall-management.md
├─ Execute commands on instance             -> references/remote-command-tat.md
├─ Create / restore snapshots               -> references/snapshot-blueprint.md
├─ Create custom images                     -> references/snapshot-blueprint.md
├─ Check traffic usage                      -> references/traffic-package.md
├─ Identify current instance (ID / IP)      -> bash script/whoami.sh [--id | --ip]
└─ Other operations                         -> tccli lighthouse --help
```

## Operation Safety

| Risk | Operations | Confirmation |
|------|-----------|--------------|
| High | Delete instance, apply snapshot, delete snapshot/blueprint | Double confirm, state irreversibility |
| Medium | Stop/reboot instance, modify firewall, run commands | Single confirm |
| Low | Query, list, describe, help | Execute directly |

Rules:
1. **Region is required** for all operations except `DescribeRegions`
2. **Query before modify** — always `Describe` first, never blind `Create` / `Delete`
3. **Use real IDs** — get InstanceId from `DescribeInstances`, never use placeholders
4. **Verify parameters** — run `--help` when unsure about parameter names or formats
5. Lighthouse and CVM are separate products — do NOT mix their APIs
6. **Create means new** — when user asks to "create" / "deploy" / "set up" something (e.g., "create a server", "deploy an app"), create a NEW instance by default. Do NOT use existing instances unless the user explicitly specifies an existing instance ID.

## Common Regions

| Code | Location |
|------|----------|
| ap-beijing | Beijing |
| ap-shanghai | Shanghai |
| ap-guangzhou | Guangzhou |
| ap-chengdu | Chengdu |
| ap-chongqing | Chongqing |
| ap-nanjing | Nanjing |
| ap-hongkong | Hong Kong |

Run `tccli lighthouse DescribeRegions` for the full list.

## Channel Output Compatibility

Many messaging channels (WeChat, 企业微信, Slack, Teams, Telegram, etc.) apply Markdown rendering or Markdown-to-plain-text conversion before displaying messages. Common transformations that **silently corrupt output**:

- **Paired underscores** stripped: `_xxx_` → `xxx` (italic markers)
- **Paired asterisks** stripped: `*xxx*` → `xxx` (bold/italic markers)
- **Backslash escapes** consumed or displayed literally
- **URLs** with special characters mangled or truncated

This corrupts:

- **URLs** containing underscores (e.g., `redirect_url`, `app_id` in OAuth links)
- **CLI output** with underscored identifiers (e.g., `instance_name`, `secret_id`)
- **Script output** containing underscored fields or special characters

**Rules for all channel output:**

1. **URLs**: Replace `_` (underscore) with `%5F` in any URL shown to the user. For example, the OAuth authorization URL parameters like `redirect_url`, `app_id` must use `%5F` instead of `_`.
2. **CLI / script output**: Always wrap output in code blocks (triple backticks) to prevent Markdown interpretation. Prefer code blocks for any multi-line output containing underscores, asterisks, or other Markdown-sensitive characters.
3. **General text**: Avoid bare underscores and asterisks in plain text. Use backtick-wrapped inline code for any identifier containing these characters (e.g., `instance_name`, `secret_id`).
4. **Links**: When providing clickable links, ensure the full URL is inside a code block or use URL-encoding for special characters. Do not rely on Markdown link syntax `[text](url)` — the URL may be altered by the channel.

## Error Handling

1. Check credentials: `tccli lighthouse DescribeRegions`
2. Verify the region parameter
3. Run `tccli lighthouse <Action> --help` to confirm parameter format
4. Check instance status: `tccli lighthouse DescribeInstances --region <region>`

IT運用・セキュリティの人気スキル

钟馗.skillIT運用・セキュリティ

钟馗.Skill——会更新漏洞库的安全审查专家。直来直去、快刀斩乱麻,三层审查(静态审计/行为模拟/供应链溯源)覆盖12类风险,输出结构化安全裁定(✅干净/⚠️可疑/🚫恶意)。Use when 用户说"审查这个Skill"、"安全检查"、"钟馗看下"、"审一下"、"查一下这个skill"、安装Skill前的安全评估、或需要审计SKILL.md的恶意载荷。

↓ 33.7万★ 17user_741dc82b
SkillScanIT運用・セキュリティ

使う前にスキルパッケージの安全性を調べ、結果に応じて導入を止めるスキルです。

↓ 18.3万★ 41tokauthai
Free Ride - Unlimited free AIIT運用・セキュリティ

OpenClaw に OpenRouter の無料モデルとフォールバック連鎖を設定するツールです。

↓ 13.4万★ 492Shaishav Pidadi
a ca s ca s c ca s cIT運用・セキュリティ

Parse, search, and analyze application logs across formats. Use when debugging from log files, setting up structured logging, analyzing error patterns, correlating events across services, parsing stack traces, or monitoring log output in real time.

↓ 12.5万★ -user_60e896a0
Skill ScannerIT運用・セキュリティ

Security checks for installing skills, packages, or plugins. Use BEFORE any npm install, openclaw plugins install, clawhub install, or similar install...

↓ 9.3万★ 4sudhindrat
网安技能IT運用・セキュリティ

网络安全与SRC漏洞掘金实战技能。融合「系统学习路径」与「SRC实战掘金」双模式: ①学习模式=法律→基础→工具→靶场→攻防→就业全流程; ②实战模式=直接指导在腾讯TSRC、阿里ASRC、百度BSRC等平台挖掘高价值漏洞变现。 当用户提出以下问题时触发: "我想学网络安全怎么入门""SRC漏洞怎么挖能赚钱""渗透测试需要学什么" "Web安全漏洞原理是什么""怎么准备CTF比赛""护网面试会问什么" "云安全怎么学""挖漏洞赚钱的方法""端口扫描脚本怎么写" "SQL注入怎么检测""子域名怎么枚举""XSS漏洞怎么找" "靶场怎么搭建""Kali Linux怎么用""Metasploit怎么入门" "等保测评是什么""代码审计怎么做""内网渗透怎么学" "信息泄露漏洞怎么挖""越权漏洞怎么测试""逻辑漏洞挖掘技巧" "简历怎么写才能进安全公司""安全行业面试题有哪些" "Burp Suite怎么用""DVWA怎么安装""Pikachu靶场搭建" "Vulhub漏洞复现""网络安全法有什么规定""CTF夺旗赛怎么参加" "AWD比赛是什么""应急响应怎么做""攻击溯源怎么搞" "数据安全怎么保障""公有云安全怎么防护""私有云攻防怎么做" "云原生安全是什么"。

↓ 8万★ 16user_d2cc4baf
人人都能成为黑客v2.0(Lvan)IT運用・セキュリティ

Unified Web penetration testing and SRC vulnerability hunting Skill. Model-driven threat modeling (12 dimensions), JSON 字段规范 state persistence, SRC/补天 compliant reporting with confirmed gate (3-layer determination). Use when user asks for authorized penetration testing, vulnerability assessment, SRC hunting (补天/Butian/vendor SRC/CNVD/众测), bug bounty, security evaluation with explicit target URL, or wants operational Recon→PoC→Report workflow. Do NOT use for CTF challenges, unauthorized testing, mobile app testing, infrastructure scanning, or social engineering.

↓ 5.7万★ 37user_a730098d
skill-vetterIT運用・セキュリティ

Security-first skill vetting for AI agents. Use before installing any skill from ClawdHub, GitHub, or other sources. Checks for red flags, permission scope, and suspicious patterns.

↓ 5.4万★ -user_814dbe54

データ月:2026-10 · ダウンロード数とスター数は公開スキルレジストリ(ClawHub、SkillHub)から月単位で集計しています。詳しくはデータの方法論をご覧ください。