ashare-market-data-fetcher
PassAudited by ClawScan on May 10, 2026.
Overview
This skill is a coherent A-share market-data guidance skill with no malicious code shown, though users should notice its reliance on external and sometimes licensed data sources.
This appears safe from a security perspective based on the provided artifacts. Before use, confirm which data sources will be contacted, avoid unauthorized paid or licensed feeds, and verify results because market-data providers can differ in timing, coverage, and calculation口径.
Findings (3)
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.
The agent may use external public or commercial data providers to satisfy market-data requests.
The skill directs the agent to gather data from multiple external data sources. This is expected for a market-data skill, but users should keep requests scoped and understand which providers are being contacted.
先抓结构化核心数据，再抓扩展信息... 主数据源 AKShare / 巨潮资讯 / Choice / 官方链路
Confirm the ticker, date range, frequency, and source before large or paid data pulls, and check provider terms and rate limits.
Using Level-2, tick, or commercial market data may require paid accounts or licensed permissions.
The skill acknowledges that some high-precision market data requires official authorization or licensed providers. No credential capture or misuse is shown, but access rights may matter.
Level-2、逐笔、订单簿、盘口深度... 通常依赖交易所官方授权链路或持牌供应商
Only use credentials or subscriptions you control and explicitly authorize; do not assume licensed data can be freely fetched or redistributed.
It may be harder to verify the maintainer, implementation history, or future changes to the skill.
The registry metadata does not provide a source repository or homepage. There is no risky install path shown, but provenance is limited.
Source: unknown; Homepage: none
Review updates before enabling newer versions, and prefer skills with clear source links when using them in sensitive workflows.