Skill flagged — suspicious patterns detected

ClawHub Security flagged this skill as suspicious. Review the scan results before using.

amazon-sorftime-research-market-skill

v1.0.0

基于Sorftime MCP的深度选品调研。通过LLM Agent执行多维度分析:数据采集→属性标注→交叉分析→竞品VOC→壁垒评估→选品决策评估。交互式执行,输出Markdown报告和Dashboard看板。

0· 91·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Suspicious
high confidence
!
Purpose & Capability
The skill advertises integration with Sorftime MCP and the code (scripts/api_client.py) requires an API key (read from .mcp.json or SORFTIME_API_KEY) and calls https://mcp.sorftime.com. However, the registry metadata lists no required environment variables or primary credential. A legitimate Sorftime integration should declare and require the API credential; the absence in metadata is an incoherence.
Instruction Scope
SKILL.md instructs running scripts that perform data collection and render dashboards. The scripts do exactly that and call the Sorftime API. However: (1) SKILL.md repeatedly states 'scripts do not do analysis', yet run_analysis.py and related modules perform market-summary computations (price ranges, brand aggregations) — a mild scope mismatch; (2) scripts read local configuration (.mcp.json) and environment variable SORFTIME_API_KEY even though these are not declared; (3) scripts create output directories by walking up several directory levels and save reports under product-research-reports in the project root — they will write files outside the skill directory, which may be surprising to users.
Install Mechanism
There is no install spec (instruction-only install), so nothing is downloaded during installation. The package includes Python scripts which will be executed when the user runs them; that is expected and lower installation risk compared to remote downloads.
!
Credentials
The code requires a Sorftime API key (via .mcp.json or SORFTIME_API_KEY) to function, but the skill registry declares no required env vars or primary credential. This is disproportionate because network API credentials are necessary for core functionality yet not surfaced in the metadata. No other unrelated secrets are requested, but missing declaration is the main issue.
Persistence & Privilege
The skill does not set always: true and does not request persistent platform privileges. It writes files to an output directory under the project root but does not modify other skills or system-wide agent settings.
What to consider before installing
Key things to check before installing/using this skill: - Credentials: The code requires a Sorftime API key (it looks in a .mcp.json file or the environment variable SORFTIME_API_KEY). The skill metadata does NOT declare this — confirm you are comfortable providing the API key and prefer using an env var rather than a file stored in your repo. - Endpoint trust: The scripts call https://mcp.sorftime.com. Only provide an API key if you trust Sorftime and accept that data (queries, raw results) will be sent there. - File writes: Running the scripts will create a 'product-research-reports' folder under the project root (the scripts compute the project root by walking up several directory levels). Run the scripts from an appropriate working directory (or inspect/modify create_output_dir) if you do not want reports written to your home or repo root. - Review local config: Inspect any existing .mcp.json before running; it may contain embedded keys or URLs. Prefer setting SORFTIME_API_KEY in your environment instead of storing secrets in repo files. - Code review: If you have limited trust in the package source (homepage is none, source unknown), review scripts/api_client.py and run_analysis.py for behavior you are comfortable with — the code uses subprocess.run to call curl (passed as a list, so not shell-invocation) to communicate with Sorftime; this is expected but verify payloads if you need strict auditing. - Run in isolation: Consider executing the scripts in an isolated environment (container or throwaway VM) the first time to confirm behavior and file locations. If you want, I can: (a) point out the exact lines where the API key is read and where outputs are written, (b) suggest minimal edits to make required env vars explicit in SKILL.md/metadata, or (c) produce a short checklist to safely run the first data-collection run.

Like a lobster shell, security has layers — review code before you run it.

latestvk972pnsseev0b82ccwpb9z0a9n83hqz2

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments