← Back to Skills Marketplace
146
Downloads
1
Stars
0
Active Installs
3
Versions
Install in OpenClaw
/install uapp-core-index
Description
友盟 U-App 核心指标查询技能，支持通过 umeng-cli call 调用友盟 OpenAPI（gateway.open.umeng.com）的 9 个只读查询接口，涵盖账户维度所有 App 合计、单日快照（DAU/新增/启动/总用户）、活跃/新增/启动趋势、使用时长。当用户需要查询 DAU、日活、新增用户...
Usage Guidance
This skill appears to implement Umeng U-App queries via the official umeng-cli, so its core behavior is coherent. The main concerns: (1) SKILL.md asks the agent to run umeng-cli trace immediately (and to send a trace that includes any Appkey provided) — that telemetry could send identifiers/keys to Umeng without explicit user consent; (2) the install instruction includes piping a GitHub-hosted install script to sh, which you should inspect before running. Recommendations before installing/using: (a) require explicit user consent before any umeng-cli trace/telemetry, and do not automatically send appkeys; (b) review the umeng-cli source/install script or install via your package manager rather than piping remote scripts; (c) treat Appkeys and AK/SK as sensitive — prefer to enter them only when necessary and confirm where they are sent; (d) if you need stronger assurance, ask the skill author to remove or make telemetry opt-in and to provide cryptographic hashes for install artifacts. If you cannot verify these, proceed cautiously or decline to install.
Capability Analysis
Type: OpenClaw Skill
Name: uapp-core-index
Version: 1.2.0
The skill bundle contains instructions (SKILL.md) that direct the AI agent to automatically perform telemetry by running 'umeng-cli trace' commands, which include exfiltrating the user-provided 'appkey' to the CLI tool. While this may be intended for usage analytics, forcing an agent to report user-specific identifiers via prompt instructions is a high-risk behavior. Additionally, the documentation suggests a 'curl | sh' installation method from a remote GitHub repository, which is a common security risk for remote code execution.
Capability Tags
Capability Assessment
Purpose & Capability
Name/description match the runtime instructions: all operations are performed via the documented umeng-cli and the declared CLI calls/endpoints align with querying Umeng U-App metrics. Requiring the umeng-cli binary and describing AK/SK auth via umeng-cli are coherent with the stated purpose.
Instruction Scope
The SKILL.md instructs the agent to run umeng-cli trace immediately after reading the skill and to send an additional trace including the user-provided appkey before the first API call. These telemetry calls are outside the core task of fetching metrics and could transmit app identifiers or appkeys to Umeng without explicit user consent. Other instructions (login flow, call format) remain within expected scope.
Install Mechanism
The skill is instruction-only (no install spec), but it recommends installing @umengfe/umeng-cli via npm or running an official install script via curl | sh from raw.githubusercontent.com. Using GitHub raw is common, but piping a remote script to sh is higher-risk and should be reviewed before execution.
Credentials
The skill declares no env vars or unrelated credentials (good). However, it relies on umeng-cli to obtain and cache AK/SK via interactive login, and it explicitly instructs sending appkey values to umeng-cli trace. Sending an appkey (or other contextual identifiers) to a telemetry endpoint is not clearly justified by the query functionality and may be disproportionate.
Persistence & Privilege
always is false and there is no request to modify other skills or system configs. The skill suggests running umeng-cli login which stores credentials in the CLI's own cache — expected for this integration. No persistent or elevated platform privileges are requested by the skill itself.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install uapp-core-index - After installation, invoke the skill by name or use
/uapp-core-index - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.2.0
**Skill version 1.2.0 changelog**
- Major refactor: migrated from custom Python scripts and OpenAPI Python SDK to integrating the official `umeng-cli` tool.
- Removed all legacy code and custom scripts; the skill now relies solely on `umeng-cli` for data access and queries.
- SKILL.md extensively updated: now documents 9 supported umeng-cli queries, detailed parameter requirements, appkey usage, login flow, and new interface endpoints.
- Added interface documentation for account statistics, daily snapshots, multi-day trends, and usage duration queries with clear field/parameter definitions.
- Introduced umeng-cli trace (埋点) logic for skill and appkey usage tracking.
- New dependency requirement: umeng-cli must be installed on the host system.
v1.1.0
- Major documentation overhaul: improved clarity and structure for usage, parameters, and error handling.
- Added detailed multi-step usage flow and response guidance.
- Enhanced typical questions and CLI parameter mapping.
- Clarified edge cases (missing app name, data not found, date errors) and added recommended responses.
- Updated and expanded example commands for both text and JSON output.
v1.0.0
Initial public release.
- 提供友盟 App 核心指标（DAU、新增用户、活跃用户、启动次数、使用时长）自然语言问答查询入口
- 支持常用指标和时间范围的自然语言转 CLI 查询参数
- 输出文本结论与趋势数据，支持 JSON 结构化数据输出
- 多种配置文件指定方式（参数、环境变量、默认路径）
- 提供详细调用示例与典型问法映射表
Metadata
Frequently Asked Questions
What is App核心指标问答?
友盟 U-App 核心指标查询技能，支持通过 umeng-cli call 调用友盟 OpenAPI（gateway.open.umeng.com）的 9 个只读查询接口，涵盖账户维度所有 App 合计、单日快照（DAU/新增/启动/总用户）、活跃/新增/启动趋势、使用时长。当用户需要查询 DAU、日活、新增用户... It is an AI Agent Skill for Claude Code / OpenClaw, with 146 downloads so far.
How do I install App核心指标问答?
Run "/install uapp-core-index" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is App核心指标问答 free?
Yes, App核心指标问答 is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does App核心指标问答 support?
App核心指标问答 is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created App核心指标问答?
It is built and maintained by Umeng+ (@squall0925); the current version is v1.2.0.
More Skills