Massive.com CLI — Massive.com工具
v1.0.1[AI辅助] Bash CLI wrapper and OpenClaw skill for Massive's public REST API. Use when Codex or an OpenClaw agent needs to query Massive market-data endpoints from a sh...
0· 354·0 当前·0 累计
by 安全扫描
OpenClaw
可疑
medium confidenceThe skill's purpose (a Bash wrapper for Massive's public API) is plausible, but the bundle and metadata contain inconsistencies (notably the core executable is missing from the distributed files and the registry metadata omits declared env inputs), and the documented support for exec-style secret refs increases the risk surface unless the runtime sandboxing is trusted.
评估建议
Do not install or enable this skill until the packaging and metadata inconsistencies are resolved. Specifically: (1) ask the publisher to include the scripts/massive executable in the published bundle and to re-run CI/tests so you can inspect the actual script content; (2) confirm the registry metadata lists the credential env vars (MASSIVE_API_KEY_REF / MASSIVE_API_KEY) so installers know what will be required; (3) review the scripts/massive source yourself for any unexpected network endpoints ...详细分析 ▾
⚠ 用途与能力
The name/description, SKILL.md, README, and references all describe a Bash CLI (scripts/massive) that resolves OpenClaw secret refs and talks to api.massive.com. However the published bundle in this registry snapshot does not include scripts/massive (the core executable), and the registry metadata at the top lists no required env vars while agents/openai.yaml and the documentation clearly expect MASSIVE_API_KEY_REF / MASSIVE_API_KEY / MASSIVE_BASE_URL. That mismatch suggests a packaging or metadata error and makes it unclear what will actually run if installed as-is.
ℹ 指令范围
SKILL.md and references restrict network access to the Massive API origin, require redaction, and instruct the agent to resolve secrets via OpenClaw SecretRefs. Those instructions stay within the stated purpose. One noteworthy scope detail: SecretRefs explicitly support an 'exec' source (execute a command and use stdout). That behavior is expected for OpenClaw-style secret resolution but it effectively permits the runtime to execute arbitrary commands when resolving a secret ref, so it increases the trust required of the runtime and any entity that can supply secret-ref payloads.
ℹ 安装机制
This is instruction-only (no install spec), which is low risk. There are no downloads or extract steps. However the repository bundle as published appears incomplete (scripts/massive is not present in the file manifest despite being required by SKILL.md and tests; BUNDLE_MANIFEST.md explicitly calls this out as a packaging error). That packaging inconsistency should be resolved before trusting the bundle.
⚠ 凭证需求
The environment/credential requirements documented (MASSIVE_API_KEY_REF preferred, MASSIVE_API_KEY fallback, and optional MASSIVE_BASE_URL) are appropriate for a CLI that authenticates to Massive. But the registry metadata at the top claiming 'Required env vars: none' contradicts agents/openai.yaml and the SKILL.md. Additionally, supporting 'exec' secret refs means a provided secret-ref JSON can cause the runtime to run arbitrary commands to fetch secrets — acceptable if the runtime enforces sandboxing, but disproportionate if secret refs can be supplied by untrusted parties or if the runtime has no strong isolation.
✓ 持久化与权限
The skill does not request permanent presence (always:false) and does not modify other skills or global agent settings. allow_implicit_invocation is true in agent metadata, which is normal for skills and not a standalone concern here.
安全有层次，运行前请审查代码。
运行时依赖
无特殊依赖
版本
latestv1.0.12026/3/2
- Added BUNDLE_MANIFEST.md to define required files for packaged or published skill artifacts. - Updated documentation to instruct users to include all files listed in BUNDLE_MANIFEST.md when packaging or publishing. - Expanded agent rules to treat non-api.massive.com URLs as invalid unless MASSIVE_BASE_URL is explicitly set.
● 可疑
安装命令
点击复制官方npx clawhub@latest install massive
镜像加速npx clawhub@latest install massive --registry https://cn.longxiaskill.com 镜像可用
本土化适配说明
Massive.com CLI — Massive.com工具 安装说明： 安装命令：npx clawhub@latest install massive
技能文档
Use the bundled CLI before writing ad hoc curl commands. Keep requests deterministic, resolve credentials through OpenClaw-compatible secret references when available, and prefer narrow queries over broad scans.
Quick 开始
- 读取 references/openclaw-secrets.md 之前 configuring credentials.
- 读取 references/massive-api.md 当...时 choosing endpoints 或 查询 shapes.
- 读取 references/security.md 之前 changing logging, auth, 或 错误 handling.
- Run
scripts/massive health到 验证 local prerequisites 和 auth configuration. - Run
scripts/massive 获取 /v3/reference/tickers/AAPL对于 generic REST 请求. - 如果 您 包 或 发布 skill, include every path listed 在...中
BUNDLE_MANIFEST.md.
Workflow
- Resolve credentials 通过
MASSIVE_API_KEY_REF当...时 possible. - Fall back 到
MASSIVE_API_KEY仅 当...时 secret ref 不 可用. - 使用 domain shortcut 当...时 matches documented Massive endpoint.
- 使用
获取对于 任何 其他 documented REST path. - Pipe JSON 进入 downstream tools 代替 的 enabling verbose logging.
Commands
scripts/massive healthscripts/massive 获取 [--查询 键=值 ...]scripts/massive 下一个到 读取next_url从 stdin JSON 和 获取 下一个 pagescripts/massive stocks ticker-detailsscripts/massive stocks 上一个-关闭scripts/massive options contract-detailsscripts/massive forex currenciesscripts/massive crypto currenciesscripts/massive indices ticker-details
Agent Rules
- Keep 输出 在...中 JSON unless human-readable mode explicitly needed.
- 发送 diagnostics 到
stderr; treatstdout作为 data. - Never 打印 resolved secrets, auth headers, 或 raw secret-ref payloads.
- Avoid
--verbose在...中 shared logs. - Feed
next_urlback 进入获取或下一个代替 的 reconstructing 分页 manually. - Treat non-
api.massive.comabsolute URLs 作为 无效 unlessMASSIVE_BASE_URL是 explicitly changed 到 另一个 HTTPS origin.
Resources
scripts/massive: main Bash CLIBUNDLE_MANIFEST.md: 必填 file 列表 对于 packaged artifactsreferences/openclaw-secrets.md: credential 和 secret-ref contract used 由 skillreferences/massive-api.md: endpoint selection 和 请求 patternsreferences/security.md: redaction 和 operational safety constraints