investment-advisor

AdvisoryAudited by Static analysis on Apr 30, 2026.

Overview

No suspicious patterns detected.

Findings (0)

Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.

What this means

Using the skill may run the included analysis script locally when a stock-analysis request is made.

Why it was flagged

The skill expects the agent or user to run included local JavaScript code. This is disclosed and central to the stock-analysis purpose, not hidden or unrelated behavior.

Skill content
脚本位于 `{Skill Location}/scripts/analyze.mjs`,通过 `node` 执行,输出 JSON 格式数据。
Recommendation

Review the included scripts if desired, and run only the documented commands with intended stock symbols.

What this means

Stock tickers or portfolio symbols entered for analysis may be visible to the external market-data provider.

Why it was flagged

The script sends requested stock identifiers to an external finance API. This data flow is disclosed and purpose-aligned, but users should know it occurs.

Skill content
const url = `https://push2his.eastmoney.com/api/qt/stock/kline/get?secid=${secid}&fields1=...&lmt=${limit}`;
Recommendation

Avoid entering sensitive portfolio details beyond the symbols needed, and confirm the external data providers are acceptable for your privacy needs.

What this means

A user could rely on generated buy/sell or position-size suggestions for real financial decisions.

Why it was flagged

The skill intentionally produces trading recommendations and position guidance, while also including a disclaimer. This is purpose-aligned but financially high-impact if over-trusted.

Skill content
建议: strong_buy / buy / hold / sell / strong_sell ... 建议仓位 ... 本skill提供的所有分析和建议仅供参考,不构成投资建议。
Recommendation

Treat outputs as research aids, verify against independent financial sources, and do not use them as personalized financial advice.

What this means

Users may not realize Node.js is required, and the version mismatch makes provenance slightly less clear.

Why it was flagged

The package declares a Node-based entry point and a package version that differs from the registry version 1.0.0, while the registry metadata lists no required binaries. This is an under-declared prerequisite/provenance inconsistency rather than hidden behavior.

Skill content
"version": "2.0.0" ... "scripts": { "analyze": "node scripts/analyze.mjs" }
Recommendation

Declare Node.js as a required binary and align package and registry versions before publication.