Token导航 LogoToken导航TokenDH.com
研究检索需要联网clawhub未标认证来源可访问clear审计通过

ucloud-indeustry-trenducloud 行业趋势

Agent Skill

ucloud-indeustry-trend 用于查找、检索和筛选相关信息,适合在 OpenClaw 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

2,736

周安装

114

GitHub Stars

公开资料未说明

下载量

912
OpenClaw

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

MIT-0

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:ucloud-indeustry-trend(ucloud 行业趋势)
来源仓库:https://github.com/lious68/ucloud-indeustry-trend
安装命令:
openclaw skills install ucloud-indeustry-trend
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install ucloud-indeustry-trend

简介

ucloud-indeustry-trend 追踪 UCloud 行业动态,包括新技术趋势与客户需求变化。

  • 适用于市场研究、竞品分析和商业机会挖掘的信息收集场景。
  • 按 30–60 天周期更新数据,提供融资事件与商业模式演变洞察。
  • 返回结果为聚合摘要,不保证实时性,需人工交叉验证关键结论。
  • 建议结合其他信源判断趋势可靠性,避免单一依赖本技能输出。

SKILL.md

name
ucloud-indeustry-trend
description
UCloud industry trend radar for tracking the latest 30-60 day changes, new customer demand, new business models, solution shifts, high-value financings, and notable teams across AI, cloud, semiconductor, overseas expansion, quant, and data center industries. Use when Codex needs to judge whether an industry solution deck is still current, produce an industry-by-industry trend brief with dated sources, refresh pre-sales messaging, identify which companies and teams are newly worth tracking, or update a solution package based on recent market movement.

Industry Trend Radar

Overview

Research recent market movement for one or more industries, then turn that research into a concise, dated brief that is directly usable for pre-sales, solution refresh, strategy review, or internal enablement.

Always treat this as a live research task. For any request about "latest", "recent", "this month", or "the past 1-2 months", browse the web and anchor the answer to exact dates.

Workflow

  1. Normalize the industry list.

Use the user's original wording when presenting results, but map each item to the closest entry in references/industry-map.md so the search terms and watch points are consistent.

  1. Fix the observation window.

Default to the latest 60 days unless the user gives a different window. State the exact start date and end date in the output.

  1. Search broadly, then narrow.

Start with recent news and official sources for each industry. Prefer primary or high-authority evidence such as:

  • official company blogs and product release notes
  • earnings calls and investor materials
  • regulators, exchanges, and policy announcements
  • major cloud, chip, AI, robotics, or e-commerce platforms
  • well-established industry media and research houses
  • financing announcements, investor newsrooms, and startup databases when the user wants company momentum signals
  1. Separate facts from inference.

For each industry, distinguish:

  • what changed
  • why it matters
  • what it likely means for customer demand, buying criteria, or solution packaging

If a point is inferred from multiple signals rather than stated directly by a source, label it clearly as an inference.

  1. Focus on commercial impact.

Do not stop at trend description. Translate each industry update into:

  • likely new customer demand
  • likely new buying or delivery models
  • what should change in a solution deck, proposal, pricing story, or positioning
  1. Add company momentum signals.

For each industry, check whether the past 30-60 days include one or more high-value financings or especially important teams worth tracking.

Use the rules in references/funding-and-team-signals.md to decide:

  • which financings are commercially meaningful
  • which teams or companies are worth naming even without a financing event
  • how to explain why that company now matters for strategy, competition, channel, or customer demand

If there is no meaningful financing or standout team in the observation window, say so explicitly instead of padding the answer.

  1. Keep the answer high signal.

For each industry, prefer 3-5 meaningful changes over a long list of weak headlines. Merge duplicate signals into one conclusion when they point to the same shift.

Research Rules

  • Always browse for temporally unstable topics.
  • Use exact dates such as 2026-03-01 to 2026-04-23, not relative phrases alone.
  • Use both Chinese and English search terms when the industry is global or export-related.
  • Prefer sources published inside the observation window, but allow slightly older background sources when needed to explain why a new change matters.
  • Include source links in the final answer.
  • Flag low-confidence industries when the signal volume is thin.
  • If the user asks for many industries at once, keep the writeup compact and prioritize changes that affect solution strategy, demand, procurement, deployment, compliance, pricing, go-to-market, financing, or key company momentum.

Output Shape

Use the structure in references/output-template.md.

At minimum, each industry section should include:

  • one-paragraph judgment
  • recent changes or trends
  • new customer demand signals
  • new model, channel, procurement, or delivery changes
  • one high-value financing if one exists
  • one or more notable teams or companies worth tracking
  • impact on solution packaging or pre-sales messaging
  • dated sources

What To Emphasize By Default

Unless the user asks for a different lens, bias the analysis toward:

  • pre-sales and solution refresh
  • what changed in the last 30-60 days
  • evidence that affects budget, urgency, or buying criteria
  • productization, deployment, compliance, or ROI expectations
  • financings and teams that signal where capital, talent, and customer momentum are concentrating
  • whether the old industry narrative is now stale

Industry Set For This Team

The default industry set currently includes:

  • AI基模
  • AI行模-投顾金融
  • AI agent
  • AI机器人
  • AI智能硬件
  • AI应用
  • 出海-加速器
  • 出海-IP代理
  • 出海-互联网
  • 出海-安防
  • 出海-跨境电商
  • 量化
  • 芯片
  • 集团云、私有云
  • 智算云
  • 数据中心

Use the mappings in references/industry-map.md for aliases, search hints, and watch points.

Response Style

  • Write in Chinese unless the user asks otherwise.
  • Be decisive and commercial, not academic.
  • Surface contradictions when the market signal is mixed.
  • End with a short 方案更新建议 block when the task is tied to sales, pre-sales, or行业方案.

适合场景

01

OpenClaw 用户查找和安装 Skill 时

02

用户想查找某类 Agent Skill 时

03

需要根据任务场景推荐可安装能力包时

04

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

OpenClaw

77.99%
按下载量换算711

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills